I did some more checking, and am now finding that other .js & .css files from the upstream server are not being compressed as well, except that these files simply are served from the upstream server with no content-type header at all. So why does nginx not recognize the file type it is handling based on mime-type configuration when dealing with proxied files? Bryanby bavery - Nginx Mailing List - English
I have the exact situation described in the wiki for the proxy_hide_header command, where my upstream server sends my JS & CSS files with the wrong Content-Type header. The file is currently being sent with a text/html content-type from the upstream server, but I am experiencing some occasional issues with browsers not rendering the CSS and suspect it may possibly be due to not having the corby bavery - Nginx Mailing List - English