Hi, Have you tried the grace mechanism ? It allows an additional TTL when a backend is sick. If you want to mark only specific URLs as sick instead of the whole backend you can play with the saint mode.
It will definitely be tricky the way you described your issue. I'd also search CF's documentation to make sure whether caching can be tuned. Best Regards, Dridi Envoyé de mon smartphone Le 25 févr. 2013 21:31, "Jeffrey Taylor" <[email protected]> a écrit : > Ya, passing 200's on everything would be fun :) > > Thanks again Hugo, I'll set that up. > > Jeff > > > On Mon, Feb 25, 2013 at 3:28 PM, Hugo Cisneiros (Eitch) < > [email protected]> wrote: > >> On Mon, Feb 25, 2013 at 5:22 PM, Jeffrey Taylor <[email protected]> wrote: >> >>> We only actually want to do this with our video segments. The reason is, >>> if our streaming box or our ingress box crash, we start generating 404's to >>> CF. The second CF gets a 404, we're screwed for ~5 minutes. That's a >>> lifetime for live video. >>> >>> CF allows TTLs on all types of files/rules, but a 404 is a solid 5 >>> minutes cached by them. >>> >>> I'm open to other ideas! >>> >> >> Ah, if it's only these items, I think it's OK. I thought that replying >> 200 to everything should confuse crawlers, robots, users, and so on :-) >> >> Give the beresp.status and vcl_error a try. I used this a lot to generate >> temporary redirects (301) instead of 200 or 404. >> >> -- >> []'s >> Hugo >> www.devin.com.br >> >> >> _______________________________________________ >> varnish-misc mailing list >> [email protected] >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> > > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
