This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19177 - Our own "fail whale"
Summary: Our own "fail whale"
Status: NEW
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: infrastructure (show other bugs)
Version: unspecified
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-01 21:42 UTC by Alex Komoroske
Modified: 2012-10-29 00:17 UTC (History)
4 users (show)

See Also:

Attachments

Description Alex Komoroske 2012-10-01 21:42:14 UTC 
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.
Comment 1 Ryan Lane 2012-10-03 05:17:02 UTC 
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.
Comment 2 Jonathan Garbee 2012-10-29 00:17:14 UTC 
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