Issue metadata
Sign in to add a comment
|
Recursive "you need login to connect" page
Reported by
fizmat...@gmail.com,
Nov 11
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Connect to Wi-Fi with authentification page 2. Try to open any URL in Chrome. You will see page "You need open authentification page" and button "Connect" 3. Press "Connect". Chrome will open page with url like "https://192.168.10.1/login?......." and instead this page it shows you page "You need open authentification page..." again. 4. Step 3 repeats recursively What is the expected behavior? What went wrong? Chrome should open "https://192.168.10.1/login?..." page normally. If i write this url in addressbox manually, page "You need..." open. I don't need this. Did this work before? Yes Chrome version: 70.0.3538.77 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Nov 12
Thanks for filing the issue. @reporter: Could you please confirm if the issue is with other browsers also and requesting some one from Internals>Network to look into the issue.
,
Nov 12
,
Nov 13
Please collect and attach a chrome://net-export log. Instructions can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Nov 13
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 14
The issue seems to be related to specific network interaction with Chrome. Hence requesting someone from the network team to help in investigating the issue and network log is attached in comment#5. Tentatively adding Internals>Network component. Thanks.!
,
Nov 15
I see ERR_CERT_SYMANTEC_LEGACY errors when loading https://ise.kantiana.ru:8443/ in the log attached to comment #5. Opera, while using the same network stack, might not signal an error yet on Symantec certificates. It is possible that this error interacts badly with the redirect that results in a redirect loop. In any case, the server operator needs to upgrade to a different certificate. Are you operating this server? If so, try obtaining a certificate from a trusted root.
,
Dec 5
fizmatbfu: Could you please respond to comment #8? We may just have to close this issue, otherwise.
,
Dec 12
Closing for now, feel free to refile if you can provide the requested information. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Nov 12