Closed Bug 616354 Opened 14 years ago Closed 14 years ago

Send 503 + Retry-After during server upgrade

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philikon, Assigned: Atoll)

Details

When the web heads are taken down for any reason, it'd be best if any requests were answered with a 503 and a Retry-After header indicating the backoff interval in seconds. The client understands this and won't come back before that time.
unclear what zeus is doing, need to make sure we have this set up everywhere for auth and for sync
Assignee: nobody → rsoderberg
Severity: normal → blocker
Status: NEW → ASSIGNED
mrz implemented a fix that ensures that zeus responds with 503 Retry-After when no backend servers are available.  see attachment 495152 [details] in bug 600208 for details.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.