Handle X-Backoff headers

RESOLVED WORKSFORME

Status

Cloud Services
Firefox Sync: Backend
RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

({meta})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

4 years ago
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.)
Blocks: 969593

Updated

4 years ago
Whiteboard: [qa+]
Is it a potential blocker for a release ?
(Reporter)

Comment 2

4 years ago
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: --- → +
No longer blocks: 969593
Richard, do you think a patch will be ready in time for 29? thanks
(Reporter)

Comment 5

4 years ago
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)
(Reporter)

Comment 7

4 years ago
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!
moving tracking to 990834
status-firefox28: unaffected → ---
status-firefox29: affected → ---
status-firefox30: affected → ---
tracking-firefox29: + → ---
tracking-firefox30: + → ---
Resolved via bug 990834
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.