January 21, 2014 08:59AM
> Your line
>
> location \.(txt|css) {
>
> looks like a regex, but you're not telling nginx it /is/ a regex. I
> wouldn't expect anything to work until you fix that.

Apologies, that was a typo during simplification of my config. I do indeed have a ~ in my nested location block, and it's definitely matching correctly.

Everything else you've specified seems to fit my observed behaviour, so think it's just that my use case doesn't fit with the inheritance rules as they stand. Thanks for your help!
Subject Author Posted

Nested location block for merging config returns 404?

WheresWardy January 21, 2014 08:29AM

Re: Nested location block for merging config returns 404?

Jonathan Matthews January 21, 2014 08:36AM

Re: Nested location block for merging config returns 404?

WheresWardy January 21, 2014 08:40AM

Re: Nested location block for merging config returns 404?

Jonathan Matthews January 21, 2014 08:50AM

Re: Nested location block for merging config returns 404?

WheresWardy January 21, 2014 08:59AM

Re: Nested location block for merging config returns 404?

Jonathan Matthews January 21, 2014 09:12AM

Re: Nested location block for merging config returns 404?

Valentin V. Bartenev January 21, 2014 11:26AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 116
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready