Well, if the .png file contained alot of detail or was a photograph, for example, I might use the browser function "Open image in a new tab" to look at it in more detail. But if I do that with png images served by appengine, the resulting behavior -- an image download in Windows, or a quicktime logo in OS X -- makes my app look more like a high school project with a bug in it than a professional site. Rather than live with this strange behavior, I'll apply a workaround.
Side note: I see that this issue was first reported to the Chrome team 3+ years ago (issue 25293<https://code.google.com/p/chromium/issues/detail?id=25293>), so it's obviously not a priority at Google. On Tuesday, May 14, 2013 12:40:13 AM UTC-4, Julie wrote: > > Is there any particular reason why you are trying to access the png files > directly? If they are displayed in an HTML page, they work fine. > > This SO article may also help > > http://stackoverflow.com/questions/15179915/serve-static-png-files-with-an-image-png-content-type-not-image-x-png > > > > > On 14 May 2013 00:41, john <[email protected] <javascript:>> wrote: > >> Yep, my problem stems from the fact that appengine is setting content >> type to *image/x-png* instead of *image/png*. Is anyone else seeing this >> with their image uploads? Why would appengine be doing this? I suppose a >> corollary question is why can't Chrome browser handle image/x-png type... >> >> I know I can workaround things by creating a subdirectory for png files >> only -- so I can set the mime type explicitly -- but I really suspect there >> is something wrong in my setup or something else that I am missing. >> >> >> >> On Sunday, May 12, 2013 11:43:50 PM UTC-4, john wrote: >>> >>> Using curl: >>> Content-Type: image/x-png >>> >>> >>> >>> On Sunday, May 12, 2013 11:22:14 PM UTC-4, timh wrote: >>>> >>>> Use headers plugin in chrome or wget to examine headers. If it's being >>>> served with a content type of application/octet-stream it would normally >>>> be >>>> downloaded. >>>> >>>> T >>>> >>>> On Monday, May 13, 2013 9:22:40 AM UTC+8, john wrote: >>>>> >>>>> I have some .png files in a directory that is configured as a static >>>>> file handler. When I point my browser to the URL for any of the images, >>>>> the >>>>> result is not what I expect: >>>>> >>>>> - On Windows/Chrome, the image file is not displayed, but instead >>>>> it is automatically downloaded. >>>>> - On OSX/Chrome and OSX/Safari, a browser message indicates that a >>>>> Quicktime plugin is needed. When I click the "Run this time" button, >>>>> the >>>>> Quicktime logo is displayed with a big question mark in it. >>>>> >>>>> I have other GAE apps with static .png files that display in the >>>>> browser as I expect. Can anyone help me figure out why this app doesn't? >>>>> One URL which shows this behavior is http://calendar-ot.appspot.** >>>>> com/static/images/**CalendarTools.png<http://calendar-ot.appspot.com/static/images/CalendarTools.png> >>>>> . >>>>> For reference, I have pasted my app.yaml file to http://pastebin.com/* >>>>> *dRZJZRd7 <http://pastebin.com/dRZJZRd7> . >>>>> >>>>> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
