Hi,
On Mon, Jul 27, 2020 at 04:42:00AM +0300, Maxim Dounin wrote:
> Hello!
>
> On Fri, Jul 24, 2020 at 03:21:31PM +0200, Adam Volek wrote:
>
> > On 24. 07. 20 4:33, Maxim Dounin wrote:
> > > As long as the response returned isn't cacheable (either
> > > as specified in the response Cache-Control
Hello!
On Fri, Jul 24, 2020 at 03:21:31PM +0200, Adam Volek wrote:
> On 24. 07. 20 4:33, Maxim Dounin wrote:
> > As long as the response returned isn't cacheable (either
> > as specified in the response Cache-Control / Expires
> > headers, or per proxy_cache_valid), nginx won't put
> > the respon
Hi,
On 24. 07. 20 4:33, Maxim Dounin wrote:
> As long as the response returned isn't cacheable (either
> as specified in the response Cache-Control / Expires
> headers, or per proxy_cache_valid), nginx won't put
> the response into cache and will continue serving previously
> cached response till
Hello!
On Thu, Jul 23, 2020 at 08:06:36PM +0200, Adam Volek wrote:
> We're running into some strange behaviour with the
> stale-while-revalidate extension of the cache-control header
> when using nginx as a reverse proxy. When
> there is a stale response in the cache with nonzero
> stale-while
Hi,
We're running into some strange behaviour with the
stale-while-revalidate extension of the cache-control header when using
nginx as a reverse proxy. When there is a stale response in the cache
with nonzero stale-while-revalidate time, nginx attempts revalidation
but seems to ignore the up
