disable request buffering in nginx

问题:

It seems that nginx buffers requests before passing it to the updstream server,while it is OK for most cases for me it is very bad :)

My case is like this:

I have nginx as a frontend server to proxy 3 different servers:

1. apache with a typical php app
2. shaveet(a open source comet server) built by me with python and gevent
3. a file upload server built again with gevent that proxies the uploads to rackspace cloudfiles while accepting the upload from the client.

#3 is the problem, right now what I have is that nginx buffers all the request and then sends that to the file upload server which in turn sends it to cloudfiles instead of sending each chunk as it gets it (those making the upload faster as i can push 6-7MB/s to cloudfiles).

The reason I use nginx is to have 3 different domains with one IP if I can't do that I will have to move the fileupload server to another machine.

回答1:

According to Gunicorn, they suggest you use nginx to actually buffer clients and prevent slowloris attacks. So this buffering is likely a good thing. However, I do see an option further down on that link I provided where it talks about removing the proxy buffer, it's not clear if this is within nginx or not, but it looks as though it is. Of course this is under the assumption you have Gunicorn running, which you do not. Perhaps it's still useful to you.

EDIT: I did some research and that buffer disable in nginx is for outbound, long-polling data. Nginx states on their wiki site that inbound requests have to be buffered before being sent upstream.

"Note that when using the HTTP Proxy Module (or even when using FastCGI), the entire client request will be buffered in nginx before being passed on to the backend proxied servers. As a result, upload progress meters will not function correctly if they work by measuring the data received by the backend servers."

回答2:

As soon as this [1] feature is implemented, Nginx is able to act as reverse proxy without buffering for uploads (bug client requests). It should land in 1.7 which is the current mainline.

[1] http://trac.nginx.org/nginx/ticket/251

Update

This feature is available since 1.7.11 via the flag

proxy_request_buffering on | off;

http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering

回答3:

Now available in nginx since version nginx-1.7.11.

See documentation http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering

To disable buffering the upload specify

proxy_request_buffering off;

回答4:

I'd look into haproxy to fulfill this need.