Invalid content types served when using alias

Tom van der Woerdt info at
Tue Oct 23 23:50:18 UTC 2012

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. I tried to solve this with :

         add_header Content-Type text/javascript;

Now I get two Content-Type headers.

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 
--http-log-path=/var/log/nginx/access.log --pid-path=/var/run/ 

Server information :

Linux #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 


More information about the nginx-devel mailing list