Implement Handling of 5xxs, X-Weave-Backoff, Retry-After.

RESOLVED FIXED in Firefox 13

Status

Android Background Services
Android Sync
P1
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: ally, Assigned: nalexander)

Tracking

unspecified
mozilla14
All
Android
Dependency tree / graph

Firefox Tracking Flags

(firefox13 fixed, firefox14 fixed, fennec+)

Details

Comment hidden (empty)
(Reporter)

Updated

6 years ago
Assignee: nobody → rnewman
OS: Mac OS X → Android
Hardware: x86 → All
Blocks: 709341
Blocks: 718493
tracking-fennec: --- → ?

Updated

5 years ago
tracking-fennec: ? → +
(Assignee)

Updated

5 years ago
Assignee: rnewman → nalexander
(Assignee)

Comment 1

5 years ago
503 handling should be fixed by Bug 709329 and earlier work.  Key point in Bug 709329 is that ServerSyncStage.onSynchronizeFailed calls GlobalSession.handleHTTPError, which interprets X-Weave-Backoff and Retry-After headers and aborts sync when found.
(Assignee)

Comment 2

5 years ago
On 200 success, Retry-After is not valid HTTP on 200, I think, so should be ignored, but X-Weave-Backoff is still ignored.  I will get on this right now.
Status: NEW → ASSIGNED
https://hg.mozilla.org/integration/mozilla-inbound/rev/f892c7884b1e
Target Milestone: --- → mozilla14

Comment 4

5 years ago
https://hg.mozilla.org/mozilla-central/rev/f892c7884b1e
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
https://hg.mozilla.org/releases/mozilla-aurora/rev/9f553761e367
status-firefox13: --- → fixed
status-firefox14: --- → fixed
Component: Android Sync → Android Sync
Product: Mozilla Services → Android Background Services
You need to log in before you can comment on or make changes to this bug.