122
edits
(first draft) |
(→Code in a back-off: formatting fix) |
||
Line 28: | Line 28: | ||
=== Code in a back-off === | === Code in a back-off === | ||
''' | '''Every''' HTTP request to a central service from Firefox needs to have logic to recognize the symptoms of a remote service in trouble and back off appropriately. For example, Firefox Sync interprets HTTP 503 as "don't hit the server for N minutes." There is also a mechanism in Firefox Sync where the server can instruct the client via an HTTP response header to not talk to the server for N seconds. This allows inadvertent DDoS to be mitigated by fast responding with a "go away" error response from the server. | ||
Server operators should understand the back-off code that is implemented, so they are prepared to save themselves should the deployment go awry. | Server operators should understand the back-off code that is implemented, so they are prepared to save themselves should the deployment go awry. |
edits