Facing content-type issue with try_files.

Makailol Charls makailol7 at gmail.com
Tue May 6 04:39:11 UTC 2014


Could someone help me with my previous query?

Actually the problem is that when image file doesn't have an extension it
is not being served with proper content type. Instead it is served with
"application/octet-stream" content-type. Due to this browser try to
download image instead of displaying it.

Is it necessary to have an extension to image file to set proper
content-type for Nginx? Couldn't web server set the content-type from *file
type* ?


On Fri, May 2, 2014 at 10:42 AM, Makailol Charls <makailol7 at gmail.com>wrote:

> Hello,
> To serve static contents i.e. images I use try_files directive of Nginx.
> My configuration location block is as below.
>     location ~* \.(jpg|jpeg|png|gif)$ {
>         try_files $request_uri  @missingImg;
>     }
> @missingImg is named location block with proxy_* directive.
> The above configuration works fine if the image file name ends with jpg,
> gif, jpeg, png extension in disk.  When image file name(stored in disk)
> includes query string  like "example.jpg?a=123" then request to such image
> is being served with application/octet-stream content-type . Because of the
> wrong content type, image is not being displayed and browser prompt to
> download image.
> Could someone suggest me what am I doing wrong here?
> Thanks,
> Makailol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140506/3005ea02/attachment.html>

More information about the nginx mailing list