Changes

Jump to: navigation, search

Phishing Protection: Design Documentation

154 bytes added, 07:44, 2 November 2006
Client Backoff
Providing the data on the server for updates and lookups requires a fair amount of resources. To help maintain a high quality of service, it may be necessary for the update and lookup servers to ask the client to make less frequent requests. To handle this, the client watches for HTTP timeouts or errors from the server and if too many errors occur, it increases in the time between requests. If remote lookups start to fail, we fall back on using the tables provided during update requests.
Update requests happen The first update request happens at a random interval between 0-5 minutes after the browser starts. The second update request happens between 15-45 minutes later. After that, each update is once every 30 minutes by default. However, if  If the client receives an error during update, it tries again in a minute. If it receives three errors in a row, it waits for 60 minutes before trying again. If it then receives another error, it waits for 180 minutes, if it receives another error, it waits 360 minutes. It will continue to check once every 360 minutes until the server responds with a success message.
A lookup request happens on page load if the user has opted into remote checking. If a lookup request fails, we automatically fall back on a local table. If there are 3 lookup failures in a 10 minute period, we wait 10 minutes before trying again. Each successive lookup failure increases the wait by (2*last wait + 10 minutes). The maximum wait before trying again is 360 minutes.

Navigation menu