Welcome! Log In Create A New Profile

Advanced

Re: Issue with upstream

Maxim Dounin
November 16, 2010 01:30PM
Hello!

On Tue, Nov 16, 2010 at 03:02:00PM +0000, Phil Bayfield wrote:

> I had actually prefixed upstream and localhost 000 and everything else 100
> to force them to load in the correct order.
> On 1 particular domain it would throw that error unless it was loaded last,
> hence just giving it a prefix 101 solved the issue.
> Bit strange!

Addition prefixes isn't going to do anything good as nginx doesn't sort
included files (I assume you used something like "include
/path/*.conf") and they are loaded in unspecified order (as
filesystem returns them).

You have to manually preserve correct order, i.e. use something
like

include /path/to/generic/includes/*.conf;
include /path/to/virtual/hosts/*.conf;

Maxim Dounin

p.s. Please do not top-post. Thank you.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

Issue with upstream

Phil Bayfield November 16, 2010 08:20AM

Re: Issue with upstream

Phil Bayfield November 16, 2010 09:30AM

Re: Issue with upstream

Maxim Dounin November 16, 2010 09:56AM

Re: Issue with upstream

Phil Bayfield November 16, 2010 10:04AM

Re: Issue with upstream

Maxim Dounin November 16, 2010 01:30PM

Re: Issue with upstream

António P. P. Almeida November 16, 2010 01:40PM

Re: Issue with upstream

Maxim Dounin November 16, 2010 02:10PM

Re: Issue with upstream

Phil Bayfield November 16, 2010 03:18PM

Re: Issue with upstream

Maxim Dounin November 16, 2010 03:40PM

Re: Issue with upstream

Phil Bayfield November 17, 2010 07:40AM

Re: Issue with upstream

Maxim Dounin January 06, 2011 03:04AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 251
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready