15 messages in ru.sysoev.nginxproxy_set_header inheritance not work...
FromSent OnAttachments
Mark Reginald JamesMar 27, 2008 11:56 pm 
Maxim DouninMar 28, 2008 2:23 am 
Mark JamesApr 10, 2008 9:04 am 
Ed WApr 10, 2008 9:24 am 
Maxim DouninApr 11, 2008 5:03 am 
Ed WApr 11, 2008 5:47 am 
Maxim DouninApr 11, 2008 6:23 am 
Ed WApr 11, 2008 6:46 am 
Mark JamesApr 11, 2008 7:06 am 
Igor SysoevApr 11, 2008 7:21 am 
Igor SysoevApr 11, 2008 7:40 am 
Maxim DouninApr 11, 2008 7:57 am 
Ed WApr 11, 2008 8:16 am 
Sean AllenApr 11, 2008 8:24 am 
Mark Reginald JamesApr 11, 2008 8:27 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:proxy_set_header inheritance not working?Actions...
From:Mark Reginald James (mrj-@public.gmane.org)
Date:Mar 27, 2008 11:56:55 pm
List:ru.sysoev.nginx

Hi,

To prevent duplication between ssl and non-ssl configs I wanted to do this:

server { listen 80; include common.conf; }

server { listen 443; ssl on; proxy_set_header X_FORWARDED_PROTO https; include common.conf; }

where common.conf has a "location /" block that has its own proxy_set_header directives.

I'm finding that in 0.5.35 the X_FORWARDED_PROTO won't be set using this arrangement.

The English proxy_set_header docs state

"This directive is inherited from the previous level when at this level are not described their directives proxy_set_header."

http://wiki.codemongers.com/NginxHttpProxyModule#proxy_set_header

Is this saying in a lost-in-translation way that inheritance only happens when there are no proxy_set_header directives at the lower level? This may be the case, because I've managed to get this common include arrangement working when the proxy_set_header directives in the include file are moved from "location /" to the top level of the file (which is at the server level).