Hi, I couldn't find what I was looking for in the search option. For a page that displays current time when refreshed, when the client presses and holds refresh button, nginx should serve a cached version of the page instead of getting the latest. When client stops pressing refresh and waits for X ms, then refreshes again, I should see the newest time. Is there an option for this in nginx?by nurettin - Nginx Mailing List - English
Thanks a lot proxy_buffers 8 2m; proxy_buffer_size 10m; proxy_busy_buffers_size 10m; Now the response gets cached properly.by nurettin - Nginx Mailing List - English
Here's the related configuration: proxy_cache_path /var/www/cache levels=1:2 keys_zone=kendi-cache:1000m max_size=10000m; proxy_cache_key "$request_uri|$request_body"; When I send small requests, nginx works great. When I send a large post request (long uri) I get these logs: I have debug on error.log, here's the output: 2013/01/08 13:50:25 32765#0: *1 cache key too larby nurettin - Nginx Mailing List - English
Hi Maxim Dounin! The proxy already caches small post responses. My cache key is request uri and body. I just don't know how to increase the buffer.by nurettin - Nginx Mailing List - English
Bizde olduğu gibi CentOS veya RedHat sunucuları kullanıyorlarsa rpm ya da rpm-src paketleri eskidir, fakat RedHat güvenlik merkezinden yeni sürümde yapılan hata düzeltmeleri eski sürüme uyarlanmış şekilde gelir. Muhtemelen kendi eklentilerini de yazıyorlardır. O yazan sürüm numarasına aldanmamak lazım.by nurettin - Türkçe Topluluğu
I'm using an old version of nginx (0.8) on centos as reverse proxy for caching POST requests in front of two upstream servers. The servers are built for receiving post requests and returning media, sometimes 10 MB in size. When the responses are small, nginx caches work fine. When I get a 2 MB response, nginx doesn't cache the POST response. I tried increasing proxy buffer size and busy buby nurettin - Nginx Mailing List - English