Maxim, one last piece of advice requested. Would it be more proper to turn
off i-m-s in the request body (by setting proxy_pass_request_headers to off
in the downstream server configuration) instead of turning it off on the
upstream server? I think that's more correct behavior, but I'm not sure.
The 304 response from the upstream server ended up being the culprit. If I
changed the upstream server to have 'if_modified_since off;" and thus always
respond with a 200 and the content, the problem is resolved. To freshen the
mirror, I can then simply remove the mirrored content from the downstre
Maxim, thank you for the prompt response. I am entirely willing to believe
that this is a misconfiguration, but I cannot figure out what I've
misconfigured. The upstream server shows no errors in its error log; its
access log does a 200 for the first GET, and 304's for subsequent GETs. The
downstre
OK, I just tracked this down to whether the proxy_pass value refers to a
load-balancing upstream collection (as I'm doing above) vs. a hard-coded
reference to one server. So, if I change the proxy_pass config value to
refer to http://download.foobar.com instead of http://download_servers,
everythi
More details:
nginx version: nginx/1.4.1 (Ubuntu)
TLS SNI support enabled
configure arguments: --prefix=/usr/share/nginx
--conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log
--http-client-body-temp-path=/var/lib/nginx/body
--http-fastcgi-temp-path=/var/lib/nginx/fastcgi
--ht
Hello. I have two nginx instances - let's call them upstream and downstream.
Both are running Ubuntu 13.10 64-bit and nginx 1.4.1. I want to use
proxy_store to mirror some rarely-changing files from upstream to
downstream.
On the downstream server, I have created a /var/www directory owned by
www-
