DescriptionAdjust 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
TEST=Less Chrome To Mobile failures, additional insightful logging.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=155317
Patch Set 1 #Patch Set 2 : Additional error logging and mitigation. #Patch Set 3 : Add generic errorCode enum, always log SEND_[SUCCESS|ERROR]. #Patch Set 4 : Fix clang error. #
Total comments: 2
Patch Set 5 : Address comment. #Messages
Total messages: 11 (0 generated)
|