This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When we get a 503 or other problem due to site capacity issues or the servers being down, it would be great to have our own nicely-styled error page (instead of just an undecorated page.
This would likely need to be served directly by fastly. If we're falling down, we'll probably be timing out and not able to serve anything. Fastly would be serving the 500s.
It looks like this could be done using the Response Object [1] from Fastly's API. [1] http://www.fastly.com/docs/api#response_object