Hacker News Reader

You've found a kind "trap street". This disambiguates the error message generated from Fastly vs the error message generated from an origin which happens to use varnish as well.

Edit: As to why Fastly wants to expose the relatively stock error message instead of custom text, I dont know. My guess would be Faslty (or their customers) have tooling built around parsing the http response and they're preserving compatibility.

https://twitter.com/dormando/status/1402466173778677764

my fault. I would sometimes monitor for "guru mediations" popping up to tell if we were throwing errors without it being caught by other systems. Among other reasons.

this question was already answered in the fastly outage thread.

It was to identify fastly's Varnish vs customer's Varnish.

https://news.ycombinator.com/item?id=27433139

Try searching an older branch manually. GitHub only searches the main branch.