DescriptionReland: Adjust ChromeToMobile error logging and mitigation.
A continuation of http://codereview.chromium.org/10913089
The original http://crrev.com/155317 exacerbated http://crbug.com/146826
Thus, it was reverted in http://crrev.com/155364
This CL additionally manages URLFetcher lifetimes with a ScopedVector.
Original CL Description follows:
================================================
Adjust ChromeToMobile error logging and mitigation.
Increase kMaxRetries for URLFetcher to 5 (common elsewhere).
Decrease kDelayHours for URLFetcher to 1hr (w/exp backoff).
Clear |access_token_| with new kGaiaOAuth2LoginAccessToken.
Clear |access_token_| *and devices* on OnGetTokenFailure().
Handle invalid login refresh tokens as OnGetTokenFailure().
Clear token, devices, retry on 403 (auth) search responses.
Add and log some new BAD_* UMA Metric enum values.
(407 related to Issue 146685 and perhaps Issue 137267)
LOG (Chrome, not UMA) send response data on failure.
Corresponding src/tools/histograms/histograms.xml change:
https://chromereviews.googleplex.com/4782033
BUG=102709, 120941, 146685, 146826
TEST=Less Chrome To Mobile failures, additional insightful logging.
Patch Set 1 #Patch Set 2 : Manage URLFetcher lifetimes with a ScopedVector. #
Total comments: 1
Messages
Total messages: 5 (0 generated)
|