Desktop version of bug 1140812 - our Sync client doesn't react to any backoff or retry headers. In theory the scheduler is all set to honor them (is is listening for observer notifications), so we just need the Sync engine to send them. Not clear what the priority is - hopefully the impact of *not* doing so isn't going to be user visible, but I'm sure the services team would like it and it may help improve the overall reliability.
P1 - sounds like we're going to want this as an important safety mechanism to deal with the possibility of an overloaded service.
Priority: -- → P1
Mark/Drew, can one of you take this?
Created attachment 8591493 [details] [diff] [review] 0011-Bug-1148701-React-to-Backoff-and-Retry-After-headers.patch Simple patch that has ServerClient send observer notifications upon the documented headers. Note that the scheduler already has support (and tests) for this notification.
Assignee: nobody → mhammond
Status: NEW → ASSIGNED
Attachment #8591493 - Flags: review?(adw)
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
status-firefox40: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
Comment on attachment 8591493 [details] [diff] [review] 0011-Bug-1148701-React-to-Backoff-and-Retry-After-headers.patch Approval Request Comment [Feature/regressing bug #]: readinglist [User impact if declined]: Fx might overload servers causing everyone to have a bad time [Describe test coverage new/current, TreeHerder]: New test [Risks and why]: Very low risk - limited to schedule of automatic reading list syncs. [String/UUID change made/needed]: None
status-firefox38: --- → affected
status-firefox39: --- → affected
Comment on attachment 8591493 [details] [diff] [review] 0011-Bug-1148701-React-to-Backoff-and-Retry-After-headers.patch We don't want to DOS ourself. Taking it Should be in 38 beta 5.
status-firefox39: affected → fixed
status-firefox38: affected → fixed
Setting qe-verify- since this fix seems to be already covered by automated tests.
Flags: qe-verify? → qe-verify-
You need to log in before you can comment on or make changes to this bug.