October 18, 2012 07:24AM
I would recommend that the documentation for location matching is updated http://wiki.nginx.org/HttpCoreModule#location, explicitaly the example. It should contain a conventional strings besides the root '/' of the site:

location = / {
# matches the query / only.
[ configuration A ]
}
location / {
# matches any query, since all queries begin with /, but regular
# expressions and any longer conventional blocks will be
# matched first.
[ configuration B ]
}
location ^~ /images/ {
# matches any query beginning with /images/ and halts searching,
# so regular expressions will not be checked.
[ configuration C ]
}
location /media/ {
# matches any query beginning with /media/ and continues serching,
# so regular expressions will be checked. This will be matched only if
# regular expressions don't find a match
[ configuration D ]
}
location ~* \.(gif|jpg|jpeg)$ {
# matches any request ending in gif, jpg, or jpeg. However, all
# requests to the /images/ directory will be handled by
# Configuration C.
[ configuration E ]
}

I don't know who could I ask about this, but I think that it's important that all 4 explained steps in the documentation are covered by the example.
Subject Author Posted

Nginx Location Matching Documentation Update

kustodian October 18, 2012 07:24AM

Re: Nginx Location Matching Documentation Update

VBart October 18, 2012 08:08AM

Re: Nginx Location Matching Documentation Update

Maxim Dounin October 18, 2012 08:34AM

Re: Nginx Location Matching Documentation Update

kustodian October 28, 2012 05:48PM

Re: Nginx Location Matching Documentation Update

Maxim Dounin October 29, 2012 04:28AM

Re: Nginx Location Matching Documentation Update

kustodian October 29, 2012 06:04AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 215
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