13 messages in ru.sysoev.nginxRe: Trouble with a complex rewrite
FromSent OnAttachments
Wilson BilkovichApr 2, 2007 4:40 am 
Igor SysoevApr 2, 2007 5:25 am 
Wilson BilkovichApr 2, 2007 12:14 pm 
Igor SysoevApr 2, 2007 12:46 pm 
Wilson BilkovichApr 2, 2007 12:54 pm 
Igor SysoevApr 2, 2007 1:19 pm 
Wilson BilkovichApr 2, 2007 2:10 pm 
Igor SysoevApr 2, 2007 2:26 pm 
Wilson BilkovichApr 2, 2007 4:27 pm 
Boris BartsytsApr 10, 2007 8:07 am 
Igor SysoevApr 10, 2007 12:59 pm 
Boris BartsytsApr 11, 2007 3:42 am 
Igor SysoevApr 12, 2007 1:28 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Trouble with a complex rewriteActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Apr 2, 2007 1:19:08 pm
List:ru.sysoev.nginx

On Mon, Apr 02, 2007 at 03:55:20PM -0400, Wilson Bilkovich wrote:

I have two more questions about this: 1. I can use any regular expression supported by PCRE, anywhere in my nginx config, correct?

The regexp engine is PCRE.

The regexp are supported in some directives only: "if", "rewrite", and "location".

2. When I have nested locations, such as: location / { location /api/receive { break; } some_config_option on; }

Configuration options in the outer scope (location /, in this case) are always evaluated, despite the break command? In other words, break only 'breaks' from the location / rewrite loop, not from the rest of the configuration?

If the "rewrite" directive has rewritten URI, then nginx search the new location configuration. The "break" stops this rewrite cycle.

The nested locations are not fully supported, you should use

location / { ... }

location /api/receive { ... }