I don't know what your planned workaround is, but have you considered the
Blobstore for saving your images?
>From your comment, it looks like you're using detailed/photo-quality
images, and uploading them as part of your application deployment. By
moving images to the Blobstore you don't need t
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
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 2
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 kno
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
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
