Closed Bug 987855 Opened 10 years ago Closed 10 years ago

Loop Server — Add a X-Backoff header

Categories

(Hello (Loop) :: Server, defect)

Product:
Hello (Loop)
Component:
Server
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: alexis+bugs, Unassigned)

References

Details

X-Backoff

    This header may be sent to indicate that the server is under heavy load but is still capable of servicing requests. Unlike the Retry-After header, X-Backoff may be included with any type of response, including a 200 OK.

    Clients should avoid unnecessary requests to the server for the number of seconds specified in the header value. For example, clients may avoid pre-emptively refreshing token if an X-Backoff header was recently seen.
When do you consider that we should add the X-Backoff header?
Should we monitor the database/partner response time?
Bug 969227 and https://etherpad.mozilla.org/fxa-sync-backoff-test-plan adds some insights about this.

For what I understand with Redis we will only have 503 but Partner API could send us the Backoff Header witch doesn't seams to be the case with our current partner.

Settings as invalid for now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Yes, this is not valid here :)
ok
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.