Disallowing multiple http {} blocks in nginx.conf?

Yichun Zhang (agentzh) agentzh at gmail.com
Thu Oct 10 21:39:45 UTC 2013


On Thu, Oct 10, 2013 at 1:21 PM, Maxim Dounin wrote:
> I don't thinks that it's a good idea to disallow configurations
> with multiple http{} blocks.  While this wasn't claimed to be
> supported, it allows fun things like running multiple
> configuration isolated, and e.g. makes merging configs from
> multiple servers much easier.

Is this going to get officially supported?

I totally understand the "fun part" of this usage. It's just that it's
hard to get everything exactly right, especially with 3rd-party
modules enabled. And a "fun configuration" that is not guaranteed to
always work is no longer fun at all :)

> AFAIR, as of now only one of standard modules has problems with
> this - embeeded perl, and it has appropriate "caveat emptor"
> clause in it's documentation.

Are you suggesting 3rd-party modules should always put a similar
caveat in their documentation too? That's kinda sad and can lead to
more confusions in the future because not every user reads the whole
documentation carefully enough. I hope we can have a better solution


More information about the nginx-devel mailing list