Another auth/location question - probably very simple to fix :)

[Igor Sysoev]

On Sat, Aug 16, 2008 at 02:33:33PM -0700, mike wrote:

> I will try that again when I get home but I brought this up again  
> because I realized it wasn't fully protected after all. Does it matter  
> what order of location blocks are defined ?

It matters for regex only:

http://wiki.codemongers.com/NginxHttpCoreModule#location

> On Aug 16, 2008, at 1:07 PM, Igor Sysoev <is at rambler-co.ru> wrote:
> 
> >On Sat, Aug 16, 2008 at 11:29:54PM +0400, Igor Sysoev wrote:
> >
> >>On Sat, Aug 16, 2008 at 12:05:17PM -0700, mike wrote:
> >>
> >>>On 8/16/08, Igor Sysoev <is at rambler-co.ru> wrote:
> >>>
> >>>>Have you tried
> >>>>
> >>>>-                 location ~ /wordpress/admin.* {
> >>>>+                 location ^~ /wordpress/admin {
> >>>>
> >>>>?
> >>>
> >>>yeah - it did not work. PHP (the nested fastcgi location inside of  
> >>>the
> >>>admin location) was not processing anymore.
> >>
> >>Yes, this is a bug. I'm looking how to resolve it.
> >
> >Looking at code, I've found that simple should work:
> >
> >         location /wordpress/admin {
> >
> >If nginx has found maximum static match, it look inclusive static and
> >regex locations. The matched inclusive regex location stops searching.
> >
> >It seems that inclusive locations should be documented:  forgot how  
> >they
> >works :).
> >
> >
> >-- 
> >Igor Sysoev
> >http://sysoev.ru/en/
> >

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