We have the following setup: firewall --> single nginx instance (SSL termination) --> haproxy --> multiple nginx/unicorn instances (via unix socket) Is it recommendable to turn request buffering off at the first nginx? Ideally things like uploads would be buffered at the final nginx instances. The first one is only there to terminate SSL and pass requests on to haproxy. Thanks,by joshua - Nginx Mailing List - English
A long-standing bug in Safari causes file uploads to hang when keepalive connections are improperly reused. https://bugs.webkit.org/show_bug.cgi?id=5760 In Apache, disabling keepalive support for Webkit solves this problem. Is there a way to do this with nginx? - Joshuaby joshua - Nginx Mailing List - English
Should this work? if ($http_accept == "application/xml") { keepalive_timeout 0; } Joshuaby joshua - Nginx Mailing List - English
One more question here. The proxy cache doesn't seem to return 304 Not Modified for cached items when a matching ETag is sent to the server. Is this behavior intentional and if so, is it planned to be added? Joshuaby joshua - Nginx Mailing List - English
*) Bugfix: nginx did not treat a comma as separator in the "Cache-Control" backend response header line. Aah, I missed this in the changelog. This works great now - thanks! Joshuaby joshua - Nginx Mailing List - English
Hello, I've been playing with the proxy_cache and am having trouble determining the intended behavior. First, my config: proxy_pass http://unicorn; proxy_cache assets; proxy_cache_key backend$request_uri; proxy_cache_use_stale updating error timeout invalid_header; proxy_cache_path /tmp/asset_cache levels=1:2 keys_zone=assets:10m; proxy_tby joshua - Nginx Mailing List - English