"Please try again" page should use 503 Service Unavailable, not redirect
Bug #489847 reported by
Matt Nordhoff
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Launchpad was down a few minutes ago. When you visited it, it showed the "Please try again" page (https:/
The HTTP server should have sent back the page content with a 503 Service Unavailable status code, but instead it sent back a 302 Found redirect to /offline.html on the current hostname. This is Wrong™, and less convenient for users:
* Users in web browsers can't just hit Refresh to try again, since it only reloads offline.html instead of the original page.
* I have no proof of this at all, but it probably confuses some tools that access Launchpad, causing them to present less useful error messages.
Changed in launchpad: | |
status: | New → Confirmed |
To post a comment you must log in.
The error messages inside Bazaar itself were highly confusing. I was trying to work out why it was complaining about a 302 Found...