Currently, the backoff time in data reduction proxy config is reset as soon as config is fetched successfully. However, if the fetched config is found to be bad (e.g., bad signing key, already expired), then Chrome would fetch a new config immediately after trying it. This can potentially cause traffic spikes at the config server.

Instead, Chrome should reset backoff timer only after the fetched config has been successfully used at least once. This would further reduces the chances of traffic spikes at the config server.