I've been investigating, and seems like it's related to 1.6 or so -
because 1.4.2 and 1.4.4 works perfectly with the config in the first email.
Any that can possibly reproduce this as well?
Best regards,
Lucas R
Robert Paprocki wrote:
Can we move past passive aggressive posting to a public mailing list and
actually try to accomplish something?
The nginx docs indicate the following about proxy_pass_header
"Permits passing otherwise disabled header fields from a proxied server
to a client."
'otherwise disabled header fields' are documented as the following (from
proxy_hide_header docs):
By default, nginx does not pass the header fields “Date”, “Server”,
“X-Pad”, and “X-Accel-...” from the response of a proxied server to a
client.
So I don't know why you would need to have proxy_pass_header
Cache-Control in the first place, since this wouldn't seem to be dropped
by default from the response of a proxied server to a client.
Have you tried downgrading back to 1.4.4 to confirm whatever problem
you're having doesn't exist within some other part of your
infrastructure that was potentially changed as part of your upgrade?
On 07/01/2014 01:09 AM, Jonathan Matthews wrote:
On 1 Jul 2014 11:01, "Lucas Rolff"<lu...@slcoding.com
<mailto:lu...@slcoding.com>> wrote:
So.. Where is the thing that states I can't use proxy_pass_header
cache-control, or expires? :)))
The proxy_hide_header and proxy_pass_header reference docs.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
