@Reporter: Added few IP address to Advanced TCP/IP Settings.  Could you please guide us in how to bypass them using proxy bypass field. If possible please guide us with video, this would help us in triaging the issue better.

Either this is a proxy configuration issue, or a captive portal interstitial issue.

If you go to chrome://net-internals/#proxy, does it show your expected proxy proxy bypass for IP literals?

  * If yes, then this is a captive portal interstitial problem.
  * If no, then this is an issue with the proxy configuration

@aliasgar...: Could you respond to the request in c#2 and c#3?  We need more input from you to make progress on this problem.

Dears,
my sincere apologies, I had to revert back to previous version of chrome.

The issue is, we have internal network at my company.
- Entire network sits behind a proxy network.
- I configured proxy in chrome, but wanted few internal IPs accesible without proxy.( bypass proxy for few ips)
- Now, when I tried to access those ips, i kept getting such error.

- you can reproduce such issue using the steps above.
- now question is that the internal ips work fine with previous chrome version, what proxy/network related settings are updated in newer version.

- please note that this issue only happens in the latest chrome, other browsers work fine.

Thanks.

We need a NetLog captured in the broken version of Chrome:
  https://dev.chromium.org/for-testers/providing-network-details

It would also be helpful to provide the same log for the working version of Chrome.

To my knowledge nothing has changed in Chrome relating to proxy bypass enforcement, so per comment #3 I expect the differences is the specific proxy settings seen by Chrome.

aliasgar.dps@, could you provide the info requested in comment #7 and comment #3?

Closing for lack of details. Please reopen the bug if you can provide the requested net logs for us to debug further, thanks.