nginx workers are recreated on reload (read
http://nginx.org/en/docs/control.html#reconfiguration), nothing can thus
remains from past cache at this level.
---
*B. R.*
On Wed, Jun 29, 2016 at 6:26 PM, itpp2012
wrote:
> CJ Ess Wrote:
> ---
> > O
CJ Ess Wrote:
---
> Ok, that explains it then. Does the cache survive reloads? Or does it
> need
> to requery?
See also https://forum.nginx.org/read.php?2,249249,249249#msg-249249
"When Nginx starts for the first time, and there's no cached OCSP
Ok, that explains it then. Does the cache survive reloads? Or does it need
to requery?
On Wed, Jun 29, 2016 at 1:23 AM, Kurt Cancemi
wrote:
> Hello,
>
> Nginx uses a per worker OCSP cache.
>
> On Tuesday, June 28, 2016, CJ Ess wrote:
>
>> I think I've got ocsp stapling setup correctly with Ngi
Hello,
Nginx uses a per worker OCSP cache.
On Tuesday, June 28, 2016, CJ Ess wrote:
> I think I've got ocsp stapling setup correctly with Nginx (1.9.0). I am
> seeing valid OCSP responses however if I keep querying the same server I
> also frequently see "No response". The OCSP responses are va
I think I've got ocsp stapling setup correctly with Nginx (1.9.0). I am
seeing valid OCSP responses however if I keep querying the same server I
also frequently see "No response". The OCSP responses are valid for seven
days. Is each worker doing its own OCSP query independently of the others?
Or is
