login about faq

Hi,

We are using the GetEmail function to retrieve an HTML email from a url that contains embedded image urls. We have noticed that when any of the embedded image urls return an image in jpeg/exif format instead of jpeg/jfif format (i.e., there is an exif header block and not a jfif header block), the returned image is "converted" into html instead of being interpreted as an image. The resulting email contains a broken image for the url.

The embedded image url returns a Content-type of image/jpeg, but the Chilkat software seems to be ignoring this and attempting to decode the file type by reading the data. It appears that once it sees a null character after the "Exif header", it stops processing.

Any help in figuring out how to fix this issue would be greatly appreciated.

Thanks,

Steve

asked Oct 22 '13 at 18:18

slgatff's gravatar image

slgatff
1112

edited Oct 22 '13 at 18:19


I can provide a new build for testing, but I would need to know the what build to provide. (When posting questions, please mention programming language, operating system, .NET Framework, 32-bit/64-bit or both, architecture, Visual Studio version, Perl version, Python version, or anything else that is necessary to identify what might be needed to provide a new build..)

link

answered Oct 23 '13 at 09:26

chilkat's gravatar image

chilkat ♦♦
11.8k316358420

Sorry about the missing information. We are using both 32 bit and 64 bit, C++ interface using Visual Studio 2008 on Windows Server 2008 R2.

Thanks,

Steve

link

answered Oct 23 '13 at 11:38

slgatff's gravatar image

slgatff
1112

Thanks Steve! I just turned my attention to this, but I'm having trouble getting the information I need to make the fix (which should be simple, I think). The MHT software looks at the 1st few bytes of a referenced file to see what it actually contains -- because the other information can be misleading or incorrect (usually it's not). Do you have a sample image file you can provide so I can open it in a hex editor to understand the format? If so, you may send it to support@chilkatsoft.com

link

answered Oct 23 '13 at 11:46

chilkat's gravatar image

chilkat ♦♦
11.8k316358420

I've sent a test image to support@chilkatsoft.com.

Steve

link

answered Oct 23 '13 at 11:56

slgatff's gravatar image

slgatff
1112

Thanks! I found this reference to not only solve this problem, but to prevent some future problems:

http://www.garykessler.net/library/file_sigs.html

(Oct 23 '13 at 12:09) chilkat ♦♦
link

answered Oct 23 '13 at 12:52

chilkat's gravatar image

chilkat ♦♦
11.8k316358420

Thanks for the quick turnaround on the patch. The changes you made do appear to have fixed the problem.

Steve

link

answered Oct 23 '13 at 16:06

slgatff's gravatar image

slgatff
1112

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×184
×98
×29

Asked: Oct 22 '13 at 18:18

Seen: 1,433 times

Last updated: Oct 23 '13 at 16:06

powered by OSQA