Hey all. Before I file a bugreport I'd like to consult with community to make sure whether I get the whole thing right. I use ssl_stapling_file and update that file daily. Today I discovered that one of my SSL websites returns outdated OCSP response, not the one which is in the OCSP stapling file: > openssl s_client -connect xxxx:443 -tls1 -tlsextdebug -status ... Cert Status: gby nanochelandro - Nginx Mailing List - English
Maxim Dounin Wrote: > nginx needs a client request to be able to request a > resource from a backend and to save it to the cache. I'm afraid my explanation wasn't clear enough. There's no need to make nginx able to make requests to fastcgi on it's own initiative. How it works today: A client makes a request. Nginx sees the cache has expired and issues a request to fastcgi. It takeby nanochelandro - Nginx Mailing List - English
Hello All, fastcgi_cache_use_stale is awesome, especially with "updating" parameter. But I have a feeling that it lacks a complementary parameter (or a separate setting to tune "updating" behaviour) that would instruct nginx to quickly return stale cached response also on first request (while fastcgi app is busy doing it's hard work). Currently existing behaviour is to retuby nanochelandro - Nginx Mailing List - English
Спасибо за разъяснения про варнинг. А что касается client_max_body_size в server{}, я перепроверил, действительно работает. Значит, мой глюк был. Ещё раз спасибо!by nanochelandro - Nginx Mailing List - Russian
Доброго времени суток. Имеется nginx/0.8.52. 1) Вопросы местами избитый, я долго гуглил, но вразумительного ответа не нашёл. 2010/11/01 07:28:32 4191#0: *3353 a client request body is buffered to a temporary file /tmp/php-uploads/38/02/00/0000000238, client: 192.168.0.3, server: xxxxxxxx, request: "by nanochelandro - Nginx Mailing List - Russian