We were able to resolve this by enabling proxy_buffering. The root cause for
why it started happening is still being investigated.
Thanks,
Liam
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, April 2, 2020 2:26 PM, Liam Moncur wrote:
> Hey,
> I am seeing an is
> You can just set the inactive time longer than your possible maximum
> expire time for the objects then the cache manager won't purge the
> cache files even the object is still valid but not accessed.
That's what I ended up doing. Thanks for the suggestion though.
__
> Is there any way to tie the 'inactive' time to the cache-control header
> expiration time so that pages that are cached in a certain time-window are
> always kept and not deleted until after the header expiration time?
You can just set the inactive time longer than your possible maximum expire
I've been doing some experimenting with nginx's proxy caching and
slowly working the kinks out.
>From what I read, the cache-control & expires headers take precedence
over the 'proxy_cache_valid' setting, which is great as certain pages
are valid for several hours at a time.
However, I am noticin
Hey,
I am seeing an issue where nginx seems to get stuck in a loop soon after the
above error. From the debug I am seeing:
2020/04/02 14:09:10 [error] 12875#12875: *338 SSL_read() failed (SSL:
error:1409441A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:SSL alert
number 50) while readin
Thomas Stephen Lee Wrote:
---
> Hi,
>
> does
>
> OpenSSL 1.1.1f.
>
> fix the issue ?
Yes.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,287377,287532#msg-287532
___
nginx mailing list
