Possible to serve a stale cache when backend throws a 503?
Is it possible to serve a stale cache if the backend serves a 503 like this?
Bonus if this can trigger an API or alert
Yep. We have docs on setup at https://docs.fastly.com/guides/performance-tuning/serving-stale-content
We don't have an alert hook built into these systems yet, but it would be pretty cool -- I'll pass on the idea!
Please sign in to leave a comment.