proxy_pass_header not working in 1.6.0
lucas at slcoding.com
Tue Jul 1 08:30:47 UTC 2014
I've verified that 1.4.4 works as it should, I receive the cache-control
and expires headers sent from upstream (Apache 2.4 in this case),
upgrading to nginx 1.6.0 breaks this, no config changes, nothing.
But thanks for the explanation Robert!
I'll try investigate it further to see if I can find the root cause,
since for me this is very odd that it's suddenly not sent to the client
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
> 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"<lucas at slcoding.com
>> <mailto:lucas at 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 at nginx.org
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx