This question might sound stupid, but I haven't found straight answer in the documentation. If I have 2 workers with 1024 worker connections, that gives me 2048 open connections limit. With keepalive set to 60 seconds, I could have all 2048 connections established. If clients tries to connect while there are 2048 connections established, will some of the inactive keepalive connections be drby VRider - Other discussion
No segfaults and proxy_cache_use_stale wasn't specified, so by default it was off. Dby VRider - Nginx Mailing List - English
I have nginx set as reverse proxy for Apache and for serving static files. Everything works great, except in the last few weeks I noticed that sometimes nginx returns page from cache which is 3-4 hours old. I checked the timestamp of the cache file, and it is old. This is part of the config file related to caching in nginx.conf: proxy_cache off; proxy_buffering on; proxy_buffer_by VRider - Nginx Mailing List - English
Found! :-) proxy_ignore_headers Set-Cookie; Thank you for your help, Maxim!by VRider - Nginx Mailing List - English
Thank you, Maxim, that explains a lot! Is there any option to ignore cookies? Dby VRider - Nginx Mailing List - English
I did additional research. It looks like it is not about Expire date. I created one simple PHP script to mimic the same headers to see if there will be any difference. This is what I got: ***23/Feb/2011:16:35:56 +0100 MISS Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT "GET /test2.php HTTP/1.0" (200) "Wget/by VRider - Nginx Mailing List - English
I am running nginx 0.8.54 on CentOS 5.2, In nginx.conf I have set proxy_ignore_headers Expires Cache-Control X-Accel-Expires; but still I get bunch of misses because of expire date. For example: ***22/Feb/2011:21:31:39 +0100 MISS Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT "GET /opensearch HTTP/1.1" (200) *by VRider - Nginx Mailing List - English