Comment #8 on issue 19289 by verdyp: Chrome's "Save image as..." is confused by site serving incorrect mime type http://code.google.com/p/chromium/issues/detail?id=19289
Really, I can just see that Yahoo News is serving its Comics images with: Content-Type: image/jpeg (as seen in the Javascript console, in the Ressources tab) even if their "name" (as seen in the URL), and their actual encoding is implying a GIF. The extensions in URLs is not a good indicator of file types, and many sites are known to not deliver the correct content-types, so there are "data type sniffers" within the implementation of the generic image renderer used by browsers. Note that the comic displayed changes regularly (or randomly?). So this is a YahooNews issue (or possibly a way for it to limit the reproduction of images, thinking that browsers will automatically switch to the correct image type, after looking for data signatures, in its image renderer, ignoring the MIME type in this case). Really, if Chrom uses such datatype sniffer and it already detects that the served "image/jpeg" MIME type is wrong and another MIME type is used for rendering it, it should report that somewhere to the UI (and the corrected MIME type should be visible in the Javascript console), so that you can save the image with the correct file extension. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
