Closed Bug 969228 Opened 10 years ago Closed 10 years ago

Handle X-Backoff headers

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: rnewman, Unassigned)

References

Details

(Keywords: meta, Whiteboard: [qa+]) 

Response headers from the storage and token servers are currently a heady mix of X-Weave* and X-*.

We should handle both, just in case.

https://docs.services.mozilla.com/token/apis.html#response-headers

(Android bug: Bug 969227.)
Whiteboard: [qa+]
Is it a potential blocker for a release ?
If I were in a 7am triage meeting, I wouldn't argue that it would block release, but I would take a late-beta patch.
OK. So, I will be tracking this for now.
status-firefox28: --- → unaffected
tracking-firefox29: ? → +
tracking-firefox30: --- → +
Richard, do you think a patch will be ready in time for 29? thanks
Mark, did you tackle this to your satisfaction in Bug 958447?
Flags: needinfo?(mhammond)
(In reply to Richard Newman [:rnewman] from comment #5)
> Mark, did you tackle this to your satisfaction in Bug 958447?

I think once bug 990834 is fixed everything will be rosy.
Flags: needinfo?(mhammond)
Sylvestre: feel free to track those two bugs independently; I'll morph this one into a meta bug.
Depends on: 990834, 958447
Keywords: meta
Thanks Richard!
Resolved via bug 990834
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.