> -Original Message-
> From: nginx-boun...@nginx.org [mailto:nginx-boun...@nginx.org] On Behalf Of
> Maxim Dounin
> Sent: Tuesday, February 18, 2014 4:13 AM
> To: nginx@nginx.org
> Subject: Re: Proxy pass location inheritance
>
> Hello!
>
> On Mon, Feb 17, 2014 at 09
oun...@nginx.org] On Behalf Of
Maxim Dounin
Sent: Tuesday, February 18, 2014 4:13 AM
To: nginx@nginx.org
Subject: Re: Proxy pass location inheritance
Hello!
On Mon, Feb 17, 2014 at 09:26:56PM +, Brian Hill wrote:
> So there is no precedence given to nested regex locations at all? What
>
Hello!
On Mon, Feb 17, 2014 at 09:26:56PM +, Brian Hill wrote:
> So there is no precedence given to nested regex locations at
> all? What value does nesting provide then?
Nesting is to do thins like this:
location / {
# something generic stuff here
location ~ \.jpg$ {
an option.
From: nginx-boun...@nginx.org [nginx-boun...@nginx.org] on behalf of Maxim
Dounin [mdou...@mdounin.ru]
Sent: Monday, February 17, 2014 9:30 AM
To: nginx@nginx.org
Subject: Re: Proxy pass location inheritance
Hello!
On Mon, Feb 17, 2014 at 05:15:
Hello!
On Mon, Feb 17, 2014 at 05:15:45PM +, Brian Hill wrote:
> So it sounds like my only solution is to restructure the locations to avoid
> the original match in /. I don't have access to the servers again until
> tomorrow, but I'm wondering if something like this would work:
>
> locati
d / location break things?
From: nginx-boun...@nginx.org [nginx-boun...@nginx.org] on behalf of Maxim
Dounin [mdou...@mdounin.ru]
Sent: Monday, February 17, 2014 5:13 AM
To: nginx@nginx.org
Subject: Re: Proxy pass location inheritance
Hello!
On Mon, Feb 17,
Hello!
On Mon, Feb 17, 2014 at 08:55:02AM +, Brian Hill wrote:
> Close, it's more akin to:
>
> location / {
> location ~ regex1 {
> # regex inside /
> }
> }
>
> location ~ regex2 {
> location ~ regex3 {
> # regex inside regex2
>
On Mon, Feb 17, 2014 at 08:55:02AM +, Brian Hill wrote:
Hi there,
> Regex 1 & 3 look for the same file types and are identical, but contain
> different configurations based on the parent location. Currently, regex1 is
> catching all matches, irrespective of the parent location.
>
> If I un
Is this correct, or will NGINX always give priority to the / location?
From: nginx-boun...@nginx.org [nginx-boun...@nginx.org] on behalf of Maxim
Dounin [mdou...@mdounin.ru]
Sent: Friday, February 14, 2014 4:19 AM
To: nginx@nginx.org
Subject: Re: P
Hello!
On Thu, Feb 13, 2014 at 06:43:08PM +, Brian Hill wrote:
> Hello, we are using NGINX to serve a combination of local and
> proxied content coming from both an Apache server (mostly PHP
> content) and IIS 7.5 (a handful of third party .Net
> applications). The proxy is working properl
Hello, we are using NGINX to serve a combination of local and proxied content
coming from both an Apache server (mostly PHP content) and IIS 7.5 (a handful
of third party .Net applications). The proxy is working properly for the pages
themselves, but we wanted set up a separate location block fo
11 matches
Mail list logo
