To prevent duplication between ssl and non-ssl configs
I wanted to do this:
proxy_set_header X_FORWARDED_PROTO https;
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.”
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).