On Feb 28, 2013, at 6:51 PM, Valentin V. Bartenev <vbart@nginx.com> wrote: > On Thursday 28 February 2013 21:36:23 André Cruz wrote: >> I'm also very interested in being able to configure nginx to NOT proxy the >> entire request. >> > [...] > > Actually, you can. > > http://nginx.org/r/proxy_set_body > http://nginx.org/r/proxy_pass_request_body I'by EDevil - Nginx Mailing List - English
I'm also very interested in being able to configure nginx to NOT proxy the entire request. Regarding this patch, https://github.com/alibaba/tengine/pull/91, is anything fundamentally wrong with it? I don't understand Chinese so I'm at a loss here... Best regards, André Cruz On Feb 28, 2013, at 3:16 PM, double <nginx-forum@nginx.us> wrote: >> I know nginx team are working on it. Yoby EDevil - Nginx Mailing List - English
Hello. I've just been bitten by the bug described previously here (http://mailman.nginx.org/pipermail/nginx/2010-September/022384.html). X-Accel-Redirect expects a decoded URL, which it will encode, but when non-ascii characters are present in the URI this process fails to produce the correct URL. According to this 2010 thread (http://nginx.2469901.n2.nabble.com/Bug-X-Accel-Redirect-td5510716.htby EDevil - Nginx Mailing List - English
On Jan 13, 2009, at 0:06 , Igor Clark wrote: >>> lhmwzy wrote: >>>> You can look at the way how lighttpd implements FastCGI >>>> Authorizers. >>>> >>>> 2009/1/12 Igor Clark <lists@ruby-forum.com>: >>> >>> Thanks for the reply. I was thinking about how to do it in terms of >>> nginx module architecby EDevil - Nginx Mailing List - English
On Jan 13, 2009, at 0:06 , Igor Clark wrote: >>> lhmwzy wrote: >>>> You can look at the way how lighttpd implements FastCGI >>>> Authorizers. >>>> >>>> 2009/1/12 Igor Clark <lists@ruby-forum.com>: >>> >>> Thanks for the reply. I was thinking about how to do it in terms of >>> nginx module architecby EDevil - Nginx Mailing List - English