18 messages in ru.sysoev.nginxRe: Possible rewrite regular expressi...
FromSent OnAttachments
Peter HoangJun 23, 2008 2:33 am 
RoxisJun 23, 2008 2:44 am 
Peter HoangJun 23, 2008 6:01 am 
Peter HoangJun 23, 2008 7:43 am 
Igor SysoevJun 23, 2008 7:55 am 
RoxisJun 23, 2008 7:56 am 
Peter HoangJun 23, 2008 8:01 am 
Peter HoangJun 24, 2008 8:47 am 
Igor SysoevJun 24, 2008 8:54 am 
Peter HoangJun 24, 2008 9:03 am 
Peter HoangJun 24, 2008 9:43 am 
Igor SysoevJun 24, 2008 11:01 am 
Igor SysoevJun 24, 2008 11:02 am 
Peter HoangJun 24, 2008 6:09 pm 
Peter HoangJun 24, 2008 10:01 pm 
Peter HoangJun 25, 2008 1:12 am 
Peter HoangJun 25, 2008 11:56 am 
Michal MachJul 23, 2009 4:13 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: Possible rewrite regular expression bug?Actions...
From:Peter Hoang (list@public.gmane.org)
Date:Jun 25, 2008 1:12:16 am
List:ru.sysoev.nginx

Actually, I realise that Apache has NE (no encoding) flag for RewriteRule and that's why "C%2B%2B" is passed down intact to the backend server. I'm thinking about implementing this flag in NGINX:

rewrite ^/search /search/q-$q.html last ne;

or

rewrite ^/search /search/q-$q.html ne;

I'm digging into the source code right now. However, it might be better if someone could quickly show me the right direction to achieve that.

Cheers, Peter