Welcome! Log In Create A New Profile

Advanced

location = precedence breakage

December 16, 2009 08:48AM
This worked consistently in 0.7.6x (and according to the docs, it should work):

location = /base { [stuff] }
location ^~ /base { [different stuff] }

On testing 0.8.30, accessing http://my.server/base works, but
http://my.server/base/plus/long/path/used.by.application
hangs for awhile, then returns a socket error. I even tried differentiating configuration with trailing slash:

location ^~ /base/ { [different stuff] }

...but apparently, the same results.

Logs show nothing. The access with the longer path doesn't show up in logs at all (not access, not error). I don't have debug build on hand right now, maybe I will compile one later if I have time. No crash, nginx stays up, but request utterly fails.

Any changes to location resolving code that would break the precedence between = and other operators, resulting in nginx to be confused?
Subject Author Posted

location = precedence breakage

kyleb December 16, 2009 08:48AM

Re: location = precedence breakage

kyleb December 16, 2009 08:55AM

Re: location = precedence breakage

Igor Sysoev December 16, 2009 09:00AM

Re: location = precedence breakage

kyleb December 16, 2009 09:19AM

Re: location = precedence breakage

Igor Sysoev December 16, 2009 10:06AM

Re: location = precedence breakage

kyleb December 16, 2009 12:38PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 54
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready