Thank you for your reply, Maxim. If the old workers do not exit for long time, what part should I investigate. Actually, I use nginx with my own patch. Thanks again.by zealot83 - Nginx Mailing List - English
Hello. This is the situation: I giva heavy traffic continually by using ApacheBench, say: while :; do ab -n 100000 -c 1000 'http://localhost/; done. And also I reload nginx continually by using while syntax. When looking at the master/worker process by using ps command, the number of worker processes increase in a moment. $ ps aux|grep nginx nobody 16879 0.0 0.0 4112 884 ?by zealot83 - Nginx Mailing List - English
Hi, Maxim. Can you please explain how this part could make problems for keepalive connections of backends? Thank you! 2012/3/21 Maxim Dounin <mdounin@mdounin.ru> > Hello! > > On Wed, Mar 21, 2012 at 10:53:45AM +0800, Abioy Sun wrote: > > > Hi All, > > > > In the file ngx_http_upstream.c I found some code like this: > > > > 1618 if (u->headby zealot83 - Nginx Development
Hi. You can refer echo-nginx-module written by agentzh. There's a *ngx_http_echo_subrequest.c *file in https://github.com/agentzh/echo-nginx-module There's lots of sub-request handling code in this file. I'm on the way of reading this module. Since the subrequest is itself a request. There's no difference with getting response body size of a normal request. 272 if (body_str != NULL && bby zealot83 - Nginx Development
Dear all, I heard that to process chunked request or response extra module or patch is necessary. I've met this log trying to upload a video file to nginx server: client sent "Transfer-Encoding: chunked" header while reading client request headers, client: xxxx., server: xxxx, request: "POST /xxx/xxx/xxx? HTTP/1.1", host: "xxx" And there is no other errorby zealot83 - Nginx Mailing List - English
Does have any problem with nginx-0.8.54?by zealot83 - Nginx Mailing List - English
A similar problem to below case occurred in mine. http://forum.nginx.org/read.php?2,144108,222098#msg-222098 Following is the ssl server configuration. At first I used AJP. But after I could not find a corresponding directive to proxy_ssl_session_reuse, I changed to proxy. upstream loadbalancer { server 127.0.0.1:8080; keepalive 100; } server { listen 443 default ssl; ssl on;by zealot83 - Nginx Mailing List - English
A similar problem occurred in my case. Following is the ssl server configuration. At first I used AJP. But after I could not find a corresponding directive to proxy_ssl_session_reuse, I changed to proxy. upstream loadbalancer { server 127.0.0.1:8080; keepalive 100; } server { listen 443 default ssl; ssl on; ...... location / {by zealot83 - Nginx Mailing List - English