13 messages in ru.sysoev.nginxRe: rewrite or internal redirection c...
FromSent OnAttachments
Remo LaubacherJul 29, 2007 1:45 am 
RoxisJul 29, 2007 1:55 am 
Remo LaubacherJul 29, 2007 2:03 am 
Igor SysoevJul 29, 2007 2:28 am 
Igor SysoevJul 29, 2007 2:29 am 
RoxisJul 29, 2007 2:44 am 
Igor SysoevJul 29, 2007 2:50 am 
RoxisJul 29, 2007 2:53 am 
Igor SysoevJul 29, 2007 3:13 am 
RoxisJul 29, 2007 3:25 am.gz
Igor SysoevJul 29, 2007 3:32 am 
RoxisJul 29, 2007 3:49 am 
Igor SysoevJul 29, 2007 3:58 am 
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: rewrite or internal redirection cycleActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Jul 29, 2007 3:58:20 am
List:ru.sysoev.nginx

On Sun, Jul 29, 2007 at 12:49:36PM +0200, Roxis wrote:

On Sunday 29 July 2007, Igor Sysoev wrote:

This is because you have no location that matches request and request against server level rewrite rules: it does not match regex and goes to "return 403".

ok, i understand this: location / {} rewrite ^(/download/.*)/media/(.*)\..*$ $1/mp3/$2.mp3 last; return 403;

but this: location / {} rewrite ^(/download/.*)/media/(.*)\..*$ $1/mp3/$2.mp3 break; return 403;

The server rules is stored in server null location. The server rules run at server rewrite phase, after "break" execution stops and leaves in server null location. Then these rules run again at usual rewrite phase.