I'm also interested in the explanation, as I have a bunch of servers with: upstream backend{ server localhost:8080 fail_timeout=1s; server localhost:80 backup; } And I eventually see requests being honored by localhost:80 backup server. Both servers, the live application proxyed server and the nginx based static fallback are on the same machine, and whenever localhost:by djeps - Nginx Mailing List - English
Yes, I'd expect the charset definition in content type header even if the content is gzipped. Reading the RFC2616, there is no mutually excludent rule that prohibits the charset to be declared after gzip encoding. Unfortunately, I'm using nginx 1.0.14 and cannot apply patches to it without having it gone through extensive testing and benchmarks again, we're changing a very important sectionby djeps - Nginx Mailing List - English
Yes, you're correct Maxim, I've a WURFL-based caching system that handles content compression. If I understand you correctly, the headers nginx receive from the upstream proxied server are sent without avail of the 'charset utf-8;' directive in nginx. I was wondering If nginx without third party modules would be able to append the charset portion of the Content-Type header with the correct cby djeps - Nginx Mailing List - English
Hello, I'm trying to add "charset=utf-8" to the Content-Type header. When I don't use "Accept-Encoding:gzip, deflate", all is fine. When I add the above request header, the response header excludes the charset info from the Content-Type header. I thoroughly read the documentation and it's not clear if it's by design nor why I can't have both charset info into Conby djeps - Nginx Mailing List - English