Thanks Maxim for your lights!
Please discard all the crap I wrote before and apologies to Jonathan, then.
:oP
---
*B. R.*
On Thu, Mar 24, 2016 at 6:27 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Mar 24, 2016 at 06:17:44PM +0100, B.R. wrote:
>
> > I guess the docs logic is
On Mar 23, 2016, at 2:14 PM, Francis Daly wrote:
> Any directives that inherit do not need to be repeated.
>
> If it does not work for you, that's probably due to proxy_pass not
> inheriting.
Thanks - that's it -- `proxy_pass` does not inherit, but all the
`proxy_set_header` directives in
On Tue, Mar 22, 2016 at 08:00:13PM -0400, Jonathan Vanasco wrote:
Hi there,
> Is there a syntax for nesting the two together, so the /foo/admin would
> inherit the /foo configuration without the need to redeclare everything?
>
> # something like
> location /foo {
>
apologies for the simple question, but i could only find the opposite situation
in the list archives and I haven't had to reconfigure some of these routes in
years!
i have
# works
location /foo {
proxy_pass http://127.0.0.1:6543;
}
I want to lock down