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
