New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 872021 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome Suggestions: Invalidate access token on 401

Project Member Reported by dewittj@chromium.org, Aug 7

Issue description

Zine noticed that sometimes the feed was unavailable, and this was diagnosed and fixed in  Issue 859684  - the solution was to detect 401 responses and revoke the access token from the cache.  We should do this for Chrome Suggestions (ntp tiles) as well.
 
Labels: -Pri-1 Pri-3
Histogram suggests this is not a huge problem.

For the histogram Suggestions.FetchResponseCode in the last 28 days, there were:
 - 3,364,349,734 total samples on Android and Windows stable
 - 40,252 401 responses
which is:
.001% of responses.

On Android, out of 47.5M users reporting FetchResponseCode, only 37 reported 401 responses.  It does seem that those 37 tended to have multiple responses rejected, as there were 252 individual reports.

Lowering priority accordingly.
Labels: zine-triage
Labels: -zine-triage zine-triaged

Sign in to add a comment