I was experiencing something very similar too. In my case I was using phusion-passenger. However, after looking at this thread https://code.google.com/p/phusion-passenger/issues/detail?id=569 I moved the `error_log` settings to inside `http` section and it seemed to have resolved the issue somehow... really not sure why, but would be great if the nginx guys can look into this.by yoavaner - Nginx Mailing List - English
Never mind. My mistake. I forgot to use `include fastcgi_params` This seems to work !! Fantastic. Thanks so much for the suggestion Valentin.by yoavaner - Nginx Mailing List - English
Valentin V. Bartenev Wrote: ------------------------------------------------------- > On Wednesday 21 March 2012 14:56:49 yoavaner > wrote: > [...] > > > > Is my nginx rewrite rule wrong? Is there a > way to make this work? > > > > > > Avoid using rewrites. > > > > Or avoid using nginx, but that won't be an ideal > solution obviby yoavaner - Nginx Mailing List - English
Thanks Maxim! > This a problem in rewrite handling, it inconsistently escapes $1 > in some cases but not in others. And it's not really related to > unicode, just any escaped char in uri will be enough to trigger > escaping. > This needs fixing. Good to know. Thanks. > > Is my nginx rewrite rule wrong? Is there a way to make this work? > Avoid using rewrby yoavaner - Nginx Mailing List - English
First post on the list, so please be gentle :) I asked this question on stackoverflow, but wasn't getting any love there, and then realised I should go to the source! I managed to get nginx (1.0.14) compiled with the latest PCRE (8.30), changed the rewrite rule to use UTF8, but it still fails in some cases with unicode characters. My rewrite rule is location / { try_filesby yoavaner - Nginx Mailing List - English