Is there a length limitation on file extensions?

B.R. reallfqq-nginx at
Wed Mar 9 16:15:58 UTC 2016

Are you sure this configuration gets loaded (nginx -t OK, no error on
configuration -re-loading)?

You could try to replace your types block with an empty one (to override
defaults if they are defined at upper level, or simply remove them) and add
the following directive:
default_type application/x-ms-application

You should se the Content-Encoding set to this special value by requesting
with HTTP on port 8080 and HTTPS on port 443.
If you get anything different, your request is probably served elsewhere.
*B. R.*

On Tue, Mar 8, 2016 at 9:34 PM, j.o.l <nginx-forum at> wrote:

> Thanks a lot for providing a working example. I reproduced it and yes works
> with that server block. Then I tried to change until I discovered the
> following. Here is my server block:
>         server {
>                 listen          443 ssl;
>                 listen          8080;
>                 server_name     xxx;
>                 ssl_certificate /etc/letsencrypt/live/xxx/fullchain.pem;
>                 ssl_certificate_key /etc/letsencrypt/live/xxx/privkey.pem;
>                 root /usr/local/nginx/conf/websites/xxx;
>                 autoindex on;
>                 types {
>                         application/x-ms-application application;
>                 }
>          }
> When I access that server using http, Content-Type is returned as defined,
> when accessing it via https, Content-Type is missing. Strange, isn´t it?
> Btw. I am using nginx 1.8.0.
> Posted at Nginx Forum:
> _______________________________________________
> nginx mailing list
> nginx at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list