Welcome! Log In Create A New Profile

Advanced

Re: editing a general location match to exclude one, specific instance?

J.R.
May 14, 2020 03:30PM
First, you forgot to escape the period in settings.php to settings\.php

> I'd like to edit the match to PASS that^ logged match -- as
> specifically/uniquely as possible -- but CONTINUE to 'deny all'
> for all other/remaining matches on "config".

Second, it's all in the location documentation:

http://nginx.org/en/docs/http/ngx_http_core_module.html#location

The two relevant bits are, depending on how you want to handle it:

1. If the longest matching prefix location has the “^~” modifier then
regular expressions are not checked.

2. Then regular expressions are checked, in the order of their
appearance in the configuration file. The search of regular
expressions terminates on the first match...
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

editing a general location match to exclude one, specific instance?

PGNet Dev May 14, 2020 02:12PM

Re: editing a general location match to exclude one, specific instance?

J.R. May 14, 2020 03:30PM

Re: editing a general location match to exclude one, specific instance?

PGNet Dev May 14, 2020 03:36PM

Re: editing a general location match to exclude one, specific instance?

Francis Daly May 15, 2020 03:00PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

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