Do not send HTTP request until the user logged in |
|||
Issue descriptionNone of our instance supports anonymous user anymore, so a valid OAuth2 token is always required. When a user clicks on a link directly to a task and hadn't logged in before, the web page sends 8 separate HTTP API requests that fails to load and it generates a fair amount of HTTP 401 on the server, occasionally contributing to a source of alert. AI: - Instead of sending the request, trigger a login flow automatically. This is actually a better user experience.
,
Dec 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
I think the Web UI should simply auto-login all the time, a bit like there's no "unlogged GMail UI" |
|||
►
Sign in to add a comment |
|||
Comment 1 by tandrii@chromium.org
, Dec 13 2017