Hacker News Reader

In which case, continued usage of obsolete headers is to Fastly's benefit. Turning them off saves the customer money.

For what it's worth, the author is listed as a "Developer Advocate".

No, they are getting too many small customers and too many small customers ( see the part where now with $500/mo commit you can get 20-30% discount of the list without squeezing them hard) vary on too many headers which means it is blowing holes in their caches, which is making their Varnish-as-a-Service not work as well as it used to.

So it seems they are starting to fall into the propaganda mode to paint over the issue rather than admit that it is time for them to start innovating again.

Surrogate keys and quite cache busting used to be Fastly special sauce but since 2014 it is rather standard.

This is one of the most aggressively worthless posts I've ever read.

This is literally nothing more than a minor blog post that points out that some of us are still using headers we might not need to. Finding anything else in that is utterly baffling.

Man, what did fastly do to you?

Reply on news.ycombinator.com