Welcome! Log In Create A New Profile

Advanced

Re: location = precedence breakage

Igor Sysoev
December 16, 2009 09:00AM
On Wed, Dec 16, 2009 at 08:48:38AM -0500, kyleb wrote:

> This worked consistently in 0.7.6x (and according to the docs, it should work):
>
> location = /base { }
> location ^~ /base { }
>
> 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/ { }
>
> ...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?

It should work. The problem is not in locations.


--
Igor Sysoev
http://sysoev.ru/en/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
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: 237
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