allow varnish exclusion based on http response code
Please allow us to exclude varnish caching by the http response code. My particular use case is that I am reverse proxying to another website that uses 302 redirect when a user is not logged in. If varnish has cached the 302 redirect, it continues to redirect (infinite loop) even after the user has logged in. While I can exclude all the dangerous pages by hand, it would be much better to just disable caching of all 302's. This took 1 minute to set up in fastly (trying out a free plan), but I would rather keep using you guys!
1
vote
Sam Gralla
shared this idea