Re: Strange ssl_client_certificate limitation?

14.01.21 21:29, Rene Moser wrote: Hi I have a hard time with ssl_client_certificate. I try to use vhosts with 2 separated CA in ssl_client_certificate configs but I was not able to do it as expected. The later ssl_client_certificate was not taken in effect and even more unexpected I was able to

Strange ssl_client_certificate limitation?

Hi I have a hard time with ssl_client_certificate. I try to use vhosts with 2 separated CA in ssl_client_certificate configs but I was not able to do it as expected. The later ssl_client_certificate was not taken in effect and even more unexpected I was able to use the first client cert to au

Re: proxy_cache not working anymore in 1.8

Hi On 01.06.2015 13:51, Oleksandr V. Typlyns'kyi wrote: >> Vary: * > http://nginx.org/r/proxy_cache_valid > If the header includes the "Vary" field with the special value "*", such > a response will not be cached (1.7.7). If the header includes the "Vary" > field with another value, such

proxy_cache not working anymore in 1.8

Hi We use nginx as proxy_cache and identified a different somehow weird behaviour compared to 1.6.: In some situations we get a MISS or EXPIRED in 1.8, where with the same config, same resource and same origin, we got a HIT in 1.6. The weird thing is, it does never change to a HIT even after sev