Issue metadata
Sign in to add a comment
|
Captive Portal logon broken with recent Chrome on Samsung Galaxy S4
Reported by
sreut...@gmail.com,
Apr 7 2017
|
||||||||||||||||||||||||
Issue descriptionExample URL: Steps to reproduce the problem: 1. Connect to a wifi that has a captive portal page 2. Android Pop-up prompts for logon/choose browser to open. 3. Selecting Chome. Chrome Browser opens, but blank page is shown with load progress bar stalling at about 5%. 4. After a while error page: ERR_CONNECTION_TIMED_OUT What is the expected behavior? Correct Captive Portal Page is shown in Chrome for logon to wifi What went wrong? The issue does NOT occur when choosing the stock Samsung Internet Browser, when being prompted for the browser. Also the issue does NOT occur when using the stock Chrome version that comes with the base 5.0.1 OS (Chrome 43.0.2357.93) of the Samsung Galaxy S4 (GT-I9506). Problem starts to appear after Chrome is updated to latest release from Play Store. Current only workaround is to make sure to not have latest chrome selected as default browser, so user can choose stock samsung internet browser for the portal logon (which then works). But of course not a long term solution. Did this work before? Yes Don't know. Tested working version: 43.0.2357.93 Chrome version: 57.0.2987.132 Channel: stable OS Version: 5.0.1 Flash Version:
,
Apr 7 2017
I am able to get to the logon page of the portal with recent chrome version, when i interrupt the stalling page load by touching the url bar, then clearing the request/URL by clicking on the X to the most right in the url bar and then manually entering some ip address like 8.8.8.8 as an url.
,
Apr 7 2017
,
Apr 8 2017
We need a log to see what's going on in this situation. Could you please: 1. open a Chrome tab to chrome://net-export, and click "Start Logging to Disk" 2. connect to captive portal and witness page loading stall 3. flip to chrome://net-export tab, and click "Stop Logging" 4. click "Email Log" 5. disconnect from captive portal 6. email the log to yourself and attach to this bug.
,
Apr 8 2017
I can also confirm the behavior for a Samsung Galaxy Note 4 (Android 6) with same Chrome release version
,
Apr 8 2017
Thank you for providing more feedback. Adding requester "pauljensen@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 10 2017
Samsung overrides Android's default captive portal behavior (launching the Android system CaptivePortalLogin app I wrote to browse a non-HSTS site) and instead launches the default browser to www.google.com which is an HSTS site so it's forced to HTTPS which is blackholed by most captive portals.
,
Apr 10 2017
OK, I understand (a bit). But why is the issue not existant on older Chrome release like 43.0.2357.93?
,
Apr 10 2017
oh, got it! I guess it related to this HSTS thingy, right?
,
Apr 10 2017
yes, this is why browsing to a non-HSTS site works, like 8.8.8.8 as you noticed.
,
Sep 13 2017
I have this problem too. Android : 5.0.2 Samsung A300F Chrome : 61.0.3163.81 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 Deleted