Great, thank you for that explanation, I do happen to have hundreds.
___________________________________________
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 737-7932 - office
(203) 931-5381 - mobile
http://web.yale.edu http://web.yale.edu/
On 3/23/18, 11:37 AM, "nginx on behalf of Igor Sysoev" <nginx-bounces@nginx.org on behalf of igor@sysoev.ru> wrote:
> On 23 Mar 2018, at 18:22, Friscia, Michael <michael.friscia@yale.edu> wrote:
>
> Ok, that worked out really well.
>
> For anyone following I had to go here
> https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.nginx.org_read.php-3F2-2C279172-2C279176-23msg-2D279176&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=wMvFvA1TR6LcTFxOloRtKG43AguBoxQxBCr4c8wjsWA&s=5TAabdHhJgEYksbFWVUWH3oS5BcbJr1p9qkxFKDtwIw&e=
> because our exchange server destroyed the sample URLs.
>
> But I’m not sure how the location order is mitigated. Is this because the first location match is a regex instead of just a string match?
The regex locations are checked in order of appearance.
Prefix and excact locations are checked to find the longest matching
prefix so their order has no meaning.
When you have hundreds of locations the order becomes important factor
during configuration maintainance.
--
Igor Sysoev
https://urldefense.proofpoint.com/v2/url?u=http-3A__nginx.com&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=wMvFvA1TR6LcTFxOloRtKG43AguBoxQxBCr4c8wjsWA&s=jwneREdf5OsLivujbx29wE52wALhYDW7sYRhfT3TXZs&e=
_______________________________________________
nginx mailing list
nginx@nginx.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.nginx.org_mailman_listinfo_nginx&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=wMvFvA1TR6LcTFxOloRtKG43AguBoxQxBCr4c8wjsWA&s=henjumx7PnMKjFYOwcaCn2sBKqWmMY5vz2cSfumQFX4&e=
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
