> What kind of ciphers do you use? Could you paste your ciphers > configuration there? ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS";by lpugoy - Nginx Mailing List - English
To add more information, we have the chain issue "Chain issues: Contains anchor". But removing it does not help. Some more details: https://prtsc.io/g4QVsY3PUY https://prtsc.io/FmMCjDao4p https://prtsc.io/WZksyPXucMby lpugoy - Nginx Mailing List - English
Hello. No, our site's grade is A. Our server is still processing requests correctly, so some of the requests succeed but most have an SSL error.by lpugoy - Nginx Mailing List - English
Hello. We recently renewed our SSL certificate. After reloading nginx the number of connections increased significantly even if the number of requests remained the same. Trying out the debug log there are a lot of entries similar to the following: accept: 153.185.223.172:59011 fd:5 event timer add: 5: 60000:1409550689995 reusable connection: 1 epoll add event: fd:5 op:1 ev:80002001 post evby lpugoy - Nginx Mailing List - English
> An update. I don't think that the if statement is > being entered. There are these messages in the > debug log > > > 2011/11/09 21:14:03 6397#0: *3 http script > var > 2011/11/09 21:14:03 6397#0: *3 http script > regex: "sess_id" > 2011/11/09 21:14:03 6397#0: *3 "sess_id" > does not match "", client: 10.214.99.16, servby lpugoy - Nginx Mailing List - English
lpugoy Wrote: > Hello. > > Thank you for the explanation. I now understand > the problem and it is now working. > > I want to add a condition where if a cookie with > the name sess_id is included in the request, then > the cache would be bypassed. I tried the following > > > if ($http_cookie ~* "sess_id") { > set $no_cache "1&quoby lpugoy - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Yes, nginx won't cache responses with cookies > unless you > specifically ask it to via proxy_ignore_headers > directive[1]. > > Please also note that if you do so, you may want > to also instruct > nginx to hide returned cookies from clients (via > proxy_hide_header > directiby lpugoy - Nginx Mailing List - English
I'm sorry, but I don't understand the effect of cookies on proxy caching. I'm trying to implement the same configuration as the one referred to, and I'm also having trouble in that it doesn't seem to be caching. I'm also using httperf. For every request the backend does return a different cookie. Is this what is preventing the caching from happening? In the debug log, I found some entries thatby lpugoy - Nginx Mailing List - English