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

Issue 631312 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Chrome can't login to Google-managed Starbucks hotspot

Project Member Reported by mdw@chromium.org, Jul 26 2016

Issue description

Version: 51.0.2704.81
OS: Android 5.0.0

This is a bug report from a friend. Apparently, when trying to login to a Google-managed WiFi network at Stabucks, Chrome rejects the hotspot login page cert as invalid. I realize this may not actually be a Chrome bug, but if not, let me know and I'll try to track this down with whomever is running the Google-backed WiFi networks at Starbucks.

Netlog attached.

From my friend:

"So here's a fail. In Starbucks, and I decide to log in to the WiFi network. The signin URL is www.google.com, which is of course redirected to the hotspot signin. At which point Chrome, on ,y Android device, refuses to display the page because the hotspot cert isn't Google's, and Google uses HSTS. Every piece of software involved was Google's."

If more details are needed please post here and I will ask for them from my friend.



 
chrome-net-export-log.json
315 KB View Download
Labels: Needs-Feedback
Tell them to try again (if it's within the past day or two). Someone internal happened to mention it in passing and I helped that team correct their intermediates.

Comment 2 by mdw@chromium.org, Jul 26 2016

That was fast - thanks. The problem was occurring as of 14:30 PDT today -- does that match the timeline you have in mind?

My understanding is the fix began rolling out last week. 30090898 is the internal bug and team.
Status: WontFix (was: Untriaged)
From reading the internal bug, it sounds like this is not a Chrome bug (and instead is an issue with the captive portal configuration). If that's incorrect, feel free to re-open this bug.

Sign in to add a comment