| From | Sent On | Attachments |
|---|---|---|
| mindfrost82 | Jun 10, 2010 8:58 am | |
| Boris Dolgov | Jun 10, 2010 9:25 am | |
| Rob Schultz | Jun 10, 2010 9:43 am | |
| Boris Dolgov | Jun 10, 2010 10:23 am | |
| Rob Schultz | Jun 10, 2010 10:36 am | |
| Igor Sysoev | Jun 10, 2010 10:44 am | |
| Rob Schultz | Jun 10, 2010 10:52 am |
| Subject: | Re: Disable PHP in specific directories | |
|---|---|---|
| From: | Igor Sysoev (ig...@sysoev.ru) | |
| Date: | Jun 10, 2010 10:44:16 am | |
| List: | ru.sysoev.nginx | |
On Thu, Jun 10, 2010 at 07:36:56PM +0200, Rob Schultz wrote:
On Jun 10, 2010, at 7:23 PM, Boris Dolgov wrote:
Hello!
On Thu, Jun 10, 2010 at 8:44 PM, Rob Schultz <rsch...@gmail.com> wrote:
Just for clarification it doesn't matter logically where he puts the location as long they are in the same server section. NginX uses the most specific match first no the first match found in the file. http://wiki.nginx.org/NginxHttpCoreModule#location
No. For locations, defined with regular expressions, the first match is being used. This is written in you link:
3. Regular expressions, in the order they are defined in the configuration file. 4. If #3 yielded a match, that result is used.
Thanks for correcting me. LOL i always thought more exact match even with
regular expressions matched first.
Could you define algorithm to find the most specific match for regexes, for example, what is more specific for "/dir/page1.php" - "^/dir/", "\.php$", "page\d+" ?
-- Igor Sysoev http://sysoev.ru/en/
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx





