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.
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.
Target Milestone: --- → mozilla14
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
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.