Re: Serve stale content if backend is healthy but "not too healthy"

2021-09-21 Thread Carlos Abalde
Hi Luca, As Dridi and Guillaume said, what you're looking for is something like the stale VMOD. I think the OSS approach suggested by Guillaume could be extended a little bit in order to improve performance and avoid request serialization. Problem is the final VCL is *ugly* and hard to

Re: Serve stale content if backend is healthy but "not too healthy"

2021-09-21 Thread Guillaume Quintard
Hi, As Dridi said, what you are looking for is exactly vmod_stale, but I wanted to point out that part: > We have a backend that actually proxies different services In that case, it might be good to actually have a Varnish backend for each type of backend behind the proxies. The backend

Re: Serve stale content if backend is healthy but "not too healthy"

2021-09-21 Thread Dridi Boukelmoune
On Tue, Sep 21, 2021 at 1:33 PM Luca Gervasi wrote: > > Hello everyone, > > We have a backend that actually proxies different services (mangling > the original response). Sometimes one of those backends are not > available and the general response goes from 200 to a 50x. > Is there a way to serve

Serve stale content if backend is healthy but "not too healthy"

2021-09-21 Thread Luca Gervasi
Hello everyone, We have a backend that actually proxies different services (mangling the original response). Sometimes one of those backends are not available and the general response goes from 200 to a 50x. Is there a way to serve a stale (valid) content (if present) for a request that comes