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

Issue 834945 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

version 66.0.3359.106 of Chrome breaks guest wireless login for Cisco 5508 WLC

Reported by gk.gren...@gmail.com, Apr 19 2018

Issue description

Device name: Samsung S8+

From "Settings > About Chrome"
Application version: 66.0.3359.106
Operating system: 8.0.0

URLs (if applicable):
Cisco Wireless LAN Controller 5508 (version 8.2.166.0) login page

Steps to reproduce:
(1) connect to guest SSID offered by Cisco WLC (web auth with PSK)
(2) log into guest website using username/password
(3) click connect

Expected result:
User Authorized

Actual result:
405 method not allowed

 
Components: Internals>Network
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: Triaged-Mobile TE-Hardware-Dependency
Unable to test this issue as the above mentioned device Samsung S8+ and Cisco WLC is not available with us.

Adding TE-Hardware-Dependency label for further triaging on this issue?

Requesting Internals>Network team to take a look at this and help us in triaging the issue?

Thanks!!
Labels: Needs-Feedback
Hi, can you reproduce the issue with network logging enabled? Here are some instructions:
https://dev.chromium.org/for-testers/providing-network-details

Is this a recent regression with Chrome 66 or has it always been a problem?
Reporter, could you perhaps provide the information requested in comment #4? We need it to be able to proceed.
Appears to be something in the older webpage template provided by Cisco when we initially installed.  Downloaded a newer template and that appears to have fixed the issue for us.  I will reproduce the error with logging on as soon as I get the chance though. 
Status: WontFix (was: Unconfirmed)
Closing as per comment #6: the issue is fixed with new webpage provided by Cisco. Sounds more like a non-Chrome issue. 

Feel free to file a new bug with us if you believe the issue persists on Chrome side. 

Sign in to add a comment