Issue metadata
Sign in to add a comment
|
Proxy server marked as bad but works after cleared
Reported by
petery...@gmail.com,
Nov 23 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.59 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Open chrome on latest windows 10 build using my proxy 2. In chrome://net-internals/#proxy proxy server is marked as bad 3. Websites don't load unless the bad proxy server is cleared in net-internals What is the expected behavior? Should load websites without asking for remembered credentials and should not mark proxy as bad. Edge browser works fine. What went wrong? As soon as chrome is opened my internet proxy server is marked as bad even if proxy credentials are entered into the popup box (shouldn't credentials be remembered without having to re-enter them?). Websites don't load until bad proxies are cleared from chrome://net-internals/#proxy Did this work before? N/A Chrome version: 55.0.2883.59 Channel: beta OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 The PAC script used is: http://172.16.16.2/wpad.dat failed proxy marked as bad is: Bloxx.repton.org.uk:80 see screenshots and net log
,
Dec 1 2016
Chrome marks a proxy as bad any time it fails to service a request, but direct connections work. This may happen for a request on an unusual port or if the proxy is flaky. In either case, the request has to succeed which not using the proxy.
,
Dec 8 2016
,
Dec 12 2016
@ peterycis: Can you please try as per above comment and update us accordingly. Thanks.!
,
Dec 12 2016
Hi, I'm using a school internet connection. Sorry I don't quite understand what you would like me to do exactly?
,
Dec 19 2016
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 21 2016
@peterycis: Request you to please update chrome to the latest beta or stable available and try again. Please update us with your observations.. Also can you please try the URL without using the Proxy. Thanks.!
,
Jan 9 2017
Are you still having these issues with the latest version of Chrome? If so, please attach a new net-internals log with the proxy enabled and then trying a direct connection with it disabled.
,
Jan 9 2017
Yes, the problem is still occurring on Version 56.0.2924.51 beta (64-bit). I don't think I can connect without the proxy as it is autodetected on my school internet and all traffic goes through it. See the net log where I opened chrome, then cleared bad proxies then loaded google.
,
Jan 10 2017
This looks like out of scope for TE, hence adding the respective label for it to triage further.
,
Jan 10 2017
,
Jan 10 2017
Possibly related to crbug.com/678557 ? Does the proxy information change if you open internet explorer? This might be a problem with Windows 10 API.
,
Jan 10 2017
Proxy still marked as bad when internet explorer is opened
,
Jan 18 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2017
,
Feb 13 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by davidben@chromium.org
, Nov 28 2016