Jonathan, please read Maxim's answer, which is the one going the right way.
My hypothesis proved to be wrong.
---
*B. R.*

On Thu, Mar 24, 2016 at 8:35 PM, Jonathan Vanasco <nginx@2xlp.com> wrote:

>
> On Mar 24, 2016, at 1:27 PM, Maxim Dounin wrote:
>
> In most cases this is more or less obvious when directives are not
> inherited, though docs can be a bit more clear on this.
>
>
> What is not-obvious / confusing is that the *_pass items are not
> inherited... but their associated directives from the same module are.
>
>
> On Mar 24, 2016, at 1:17 PM, B.R. wrote:
>
> This product uses a different paradigm that 'minimal configuration lines',
> and Igor has nothing against duplicated blocks, which allow direct
> understanding of what is in effect in the location block you are looking
> at, compared to horizontal/similar ones (ofc server-wide directives shall
> not and won't be redeclared at location level).
> In the modern world, use of configuration management tools, which allow
> templating, allows duplicated stanzas without trouble on configuration
> generation/deployment.
>
>
> I'm fine with that. I've been using nginx for 10 years now (!) and have a
> huge library of macros that are included into various blocks dozens of
> times.
>
> Right now I'm trying to open-source something I wrote to handle
> lets-encrypt certificate management behind nginx.
>
> For simplicity, I wanted to make a very concise nested block for the
> documents. When there are many header variables that need to be set, the
> docs can get hard for people to follow.
>
>
> _______________________________________________
> 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