New issue
Advanced search Search tips

Issue 724064 link

Starred by 5 users
Status: Archived
Owner: ----
Closed: Jun 2017
Cc:
mmenke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

URL with a raw IPv6 host doesn't respect proxy settings

Reported by yoshik...@gmail.com, May 18 2017 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9460.42.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.57 Safari/537.36

Example URL:
http://[2001:260:401:372::5f]/ip/

Steps to reproduce the problem:
1. Set a proxy
2. Access some URL with a raw IPv6 host (like http://[xxxx:xxxx::xxxx]/foo/bar)

What is the expected behavior?
Proxy should be used to access the HTTP server.

What went wrong?
Proxy is not used to access the HTTP server. Chrome connects to the server directly.

Did this work before? No 

Chrome version: 59.0.3071.57  Channel: beta
OS Version: 9460.42.0
Flash Version: Shockwave Flash 26.0 r0

Comment 1 by mmenke@chromium.org, May 18 2017

Components: -Internals>Network Internals>Network>Proxy
Labels: Needs-Feedback
I assume you aren't using a SOCKS proxy, but rather SOCKS5, HTTP, or HTTPS proxy?  SOCKS v4 doesn't support IPv6.  Note that many SOCKS v5 proxies support v4, so it could be you're using Chrome configured to use a proxy as a v4 proxy without realizing it, and just need to tell it you're using a v5 proxy to fix the issue.

Comment 2 by yoshik...@gmail.com, May 18 2017 

I checked HTTP and HTTPS proxies, and it looks both don't work. I haven't check SOCKS proxy.
Project Member

Comment 3 by sheriffbot@chromium.org, May 18 2017

Cc: mmenke@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mmenke@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

Comment 4 by eroman@chromium.org, May 18 2017

Labels: Needs-Feedback
Please provide a net log dump (https://dev.chromium.org/for-testers/providing-network-details).

There is nothing fundamentally different with IPv6 addresses going through proxy or not (modulo what Matt said about inability to use SOCKSv4).

Some possible sources of your problem:
  * Do you have a proxy bypass rules for certain IP ranges?
  * Are you using a PAC script to select the proxy? (The "host" seen in PAC script has different meanings across browsers when IPv6 literals are used -- whether bracketed or not).

Comment 5 by mge...@chromium.org, May 30 2017 

Please provide a net log dump as requested in comment 4. Without it, we won't be able to look into the problem further.

Comment 6 by mmenke@chromium.org, Jun 14 2017

Status: Archived (was: Unconfirmed)
Archiving issue, due to lack of followup.  Can't make progress without the log.  Feel free to file a new bug, with a log attached.
►

Sign in to add a comment