Show all posts by user
A portal to and from the mailing list.
Nginx reload problem - 11 years ago
Hello: I found that some nginx config option doesn't take effect after modification with reload, the following is a simple test case: nginx version: nginx/1.2.7 nginx.conf: ============================ worker_processes 1; error_log logs/error.log info; events { worker_connections 1024; } http { limit_req_zone $arg_a zone=testzone:64m rate=1r/s; server { listen 80;by lm011111 - Nginx Mailing List - English
Re: Is it possible that nginx will not buffer the client body? - 12 years ago
Hello! @yaoweibin > If you are eager for this feature, you could try my patch: > https://github.com/taobao/tengine/pull/91. This patch has been running in > our production servers. what's the nginx version your patch based on? Thanks! On Fri, Jan 11, 2013 at 5:17 PM, 姚伟斌 <yaoweibin@gmail.com> wrote: > I know nginx team are working on it. You can wait for it. > >by lm011111 - Nginx Mailing List - English
Is it possible that nginx will not buffer the client body? - 12 years ago
Hello! is it possible that nginx will not buffer the client body before handle the request to upstream? we want to use nginx as a reverse proxy to upload very very big file to the upstream, but the default behavior of nginx is to save the whole request to the local disk first before handle it to the upstream, which make the upstream impossible to process the file on the fly when the file is uploby lm011111 - Nginx Mailing List - English
Re: Nginx HttpAccessModule command invalid when rewrite command existed - 13 years ago
Thanks Igor. That is OK, and I had a think and use the following commands instead: location /entry1 { if ( ! $remote_addr ~ "^(127\.0\.0|10\.10\.10)" ) { return 403; } rewrite *** } On Wed, Nov 9, 2011 at 10:42 PM, Igor Sysoev <igor@sysoev.ru> wrote: > On Wed, Nov 09, 2011 at 10:35:44PM +0800, li zJay wrote: > > In the following simple case: > > > >by lm011111 - Nginx Mailing List - English
Re: Nginx HttpAccessModule command invalid when rewrite command existed - 13 years ago
In the following simple case: location /entry1 { allow 127.0.0.1; deny all; rewrite ***; } the allow/deny command has no effect. Is that because rewrite command works in the earlier phase? Thanks! On Wed, Nov 9, 2011 at 10:30 PM, li zJay <zjay1987@gmail.com> wrote: > In the following simple case: > > location /entry1 { > allow 127.0.0.1; > > } > &by lm011111 - Nginx Mailing List - English
Nginx HttpAccessModule command invalid when rewrite command existed - 13 years ago
In the following simple case: location /entry1 { allow 127.0.0.1; } -- 祝好 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby lm011111 - Nginx Mailing List - English
Re: nginx won't honor limit_rate - 13 years ago
Thanks Maxim Dounin! I thought that if proxy_max_temp_file_size is set to 0, all the upstream content have to be buffered in memory, and I make a test and find I'm wrong.. On Fri, Sep 30, 2011 at 11:18 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Fri, Sep 30, 2011 at 10:56:41PM +0800, li zJay wrote: > > > hello! > > > > If you want nginx to doby lm011111 - Nginx Mailing List - English
Re: nginx won't honor limit_rate - 13 years ago
hello! If you want nginx to don't touch disk, use > > proxy_max_temp_file_size 0; > > instead. This will still allow in-memory buffering and wouldn't > touch disk. > Because the client bandwidth is usually slow, in this case, tons of upstream content will be buffer in memory before sent out to client, and then the swap will be used and the server is going down soon. On Friby lm011111 - Nginx Mailing List - English
Re: nginx won't honor limit_rate - 13 years ago
set "proxy_buffering on", the upstream response may touch the disk this suffers a lot when nginx is used as a proxy to file download servers. On Thu, Sep 29, 2011 at 7:31 AM, mojiz <nginx-forum@nginx.us> wrote: > Thanks Max. > It worked! > > Posted at Nginx Forum: > http://forum.nginx.org/read.php?2,215989,215991#msg-215991 > > _______________________________by lm011111 - Nginx Mailing List - English
Re: EmbeddedPerlModule question - 13 years ago
Thank you, it works! On Thu, Sep 1, 2011 at 6:06 PM, Igor Sysoev <igor@sysoev.ru> wrote: > On Thu, Sep 01, 2011 at 06:01:31PM +0800, li zJay wrote: > > I want to access nginx $uri variable in perl, the following is my > nginx.conf > > > > worker_processes 1; > > > > > > events { > > > worker_connections 1024; > > > } > &gby lm011111 - Nginx Mailing List - English
EmbeddedPerlModule question - 13 years ago
I want to access nginx $uri variable in perl, the following is my nginx.conf worker_processes 1; > > events { > worker_connections 1024; > } > > http { > perl_set $perlvar 'sub {return "ngx_uri:$uri";}'; > > server { > listen 80; > location / { > add_header "perlvar" $perlvar; > empty_by lm011111 - Nginx Mailing List - English
Re: upload file problem (500 Internal Server Error) - 13 years ago
try this? > worker_rlimit_nofile 10000; > On Thu, Sep 1, 2011 at 4:42 PM, Piotr Polok <toplek@polok.pl> wrote: > HI, > > I'm using version: 'nginx version: nginx/1.1.0' > > While uploading file I'm getting an error: '500 Internal Server Error' > > This is an nginx.log result: > > ------ > 2011/09/01 10:39:49 28764#0: accept() failed (24: Too many openby lm011111 - Nginx Mailing List - English
Re: The request buffer in Nginx Http FcgiModule - 14 years ago
Thanks, Rob. If the the raw upload file is to be saved in the local server, Nginx has good performance. But I want to compress the upload file and split it and then transfer to another central storage system, the file is not to be stored locally. In fact, the problem is that, if there's 1000 concurrent requests, each request has 500MB post body, It's to comsume 500G temporary disk space, and itby lm011111 - Nginx Mailing List - English
Re: The request buffer in Nginx Http FcgiModule - 14 years ago
Thanks, Maxim Dounin! In fact I work with python, and I find that no matter "Nginx + FastCGI" or "Nginx + Mod_Wsgi", the nginx force to buffer the whole client request body in either memory or file system. This is really a problem for those who want to use Nginx as a file-upload server. On Thu, Mar 18, 2010 at 5:25 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Heby lm011111 - Nginx Mailing List - English
Re: The request buffer in Nginx Http FcgiModule - 14 years ago
Hello: Why the Nginx has to buffer the whole request body before send it to FastCGI Server? I tried to change the following configurations: fastcgi_buffer_size fastcgi_buffers fastcgi_busy_buffers_size fastcgi_temp_file_write_size But it didn't help. Thanks! On Thu, Mar 18, 2010 at 12:07 AM, Maxim Dounin <mdounin@mdounin.ru> wrote: > > Hello! > > On Wed, Marby lm011111 - Nginx Mailing List - English
Re: The request buffer in Nginx Http FcgiModule - 14 years ago
Why the Nginx has to buffer the whole request body before send it to FastCGI Server? I tried to change the following configurations: fastcgi_buffer_size fastcgi_buffers fastcgi_busy_buffers_size fastcgi_temp_file_write_size But it didn't help. Thanks! On Thu, Mar 18, 2010 at 12:07 AM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Wed, Mar 17, 2010 at 1by lm011111 - Nginx Mailing List - English
The request buffer in Nginx Http FcgiModule - 14 years ago
Hello everybody: When working with Fast CGI Module, I find that Nginx buffers the whole request content before send it to the FastCGI Server. For example, the client uploads a file of 10MB to Nginx, I notice that the backend Fast CGI server didn't receive any request until all the 10MB data has been upload to the Nginx. I want to upload a very very large file like a stream and process it in theby lm011111 - Nginx Mailing List - English
 |
 |
 |
 |
|