Invalid content types served when using alias

[Tom van der Woerdt]

Yes, this patch seems to work fine for me as well. Thanks!

Tom


On 10/24/12 3:59 PM, Vladimir Shebordaev wrote:
> Hi!
>
> On 24.10.2012 03:50, Tom van der Woerdt wrote:
>> Hi all,
>>
>> I'm using nginx' locations to serve a javascript file on '/client' :
>>
>>      location = /client {
>>          expires epoch;
>>          alias /path/to/a/file.js;
>>      }
>>
>> Works fine, with one major exception: it gets an octet-stream
>> Content-Type header.
>
> This is due to a bug in static module, it doesn't properly set 
> r->exten in this case, so the redirect gets default mime-type.
>
> Please try this patch
>
> Index: src/http/modules/ngx_http_static_module.c
> ===================================================================
> --- src/http/modules/ngx_http_static_module.c    (revision 4892)
> +++ src/http/modules/ngx_http_static_module.c    (working copy)
> @@ -224,6 +224,9 @@
>          return NGX_HTTP_INTERNAL_SERVER_ERROR;
>      }
>
> +    r->uri = path;
> +    ngx_http_set_exten(r);
> +
>      if (ngx_http_set_content_type(r) != NGX_OK) {
>          return NGX_HTTP_INTERNAL_SERVER_ERROR;
>      }
>
>
> It does resolve the issue for me.
>
>
>> I tried to solve this with :
>>          add_header Content-Type text/javascript;
>>
>> Now I get two Content-Type headers.
>>
>
> Sure, the ability to add a duplicate header with add_header directive 
> is to be subjected to separate design considerations.
>
> Hope it helps.
>
> Regards,
> Vladimir
>
>
>> The raw response:
>>
>> < HTTP/1.1 200 OK
>> < Server: nginx/1.3.6
>> < Date: Tue, 23 Oct 2012 23:42:27 GMT
>> < Content-Type: application/octet-stream
>> < Content-Length: 23245
>> < Last-Modified: Sat, 20 Oct 2012 00:09:12 GMT
>> < Connection: keep-alive
>> < ETag: "5081eba8-5acd"
>> < Expires: Thu, 01 Jan 1970 00:00:01 GMT
>> < Cache-Control: no-cache
>> < Content-Type: text/javascript
>> < Accept-Ranges: bytes
>>
>> nginx information :
>>
>> nginx version: nginx/1.3.6
>> built by gcc 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC)
>> TLS SNI support enabled
>> configure arguments: --user=nginx --group=nginx
>> --with-http_ssl_module --with-http_gzip_static_module
>> --with-http_secure_link_module --with-http_realip_module
>> --with-http_stub_status_module --with-ipv6
>> --with-openssl=/root/libraries/openssl-1.0.1c/
>> --prefix=/etc/nginx/ --sbin-path=/usr/sbin/nginx
>> --conf-path=/etc/nginx/nginx.conf
>> --error-log-path=/var/log/nginx/error.log
>> --http-log-path=/var/log/nginx/access.log
>> --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock
>> --http-client-body-temp-path=/var/cache/nginx/client_temp
>> --http-proxy-temp-path=/var/cache/nginx/proxy_temp
>> --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp
>> --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp
>> --http-scgi-temp-path=/var/cache/nginx/scgi_temp
>>
>> Server information :
>>
>> Linux hostname.goes.here 2.6.32-279.5.2.el6.centos.plus.i686 #1
>> SMP Thu Aug 23 22:13:33 UTC 2012 i686 i686 i386 GNU/Linux
>>
>> It's not a major issue for me (browsers will accept octet-stream
>> just fine) but might be annoying for other people, should they
>> ever run into this.
>>
>> Tom
>>
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel