834049 - SOCKS requests not retried with available ipv4 addresses if SOCKS gateway returns "address family not supported"

Status: UNCONFIRMED

(Core :: Networking: Proxy, defect, P3)

Description

[Paul Forgey]

Attachment: filtered pcap of SOCKS conversation

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130116073211

Steps to reproduce:

set up a SOCKS 5 proxy which only supports ipv4 addresses, try to visit "www.google.com"

Firefox 18.0.1, Windows 7 (amd64)



Actual results:

www.google.com resolves to both ipv4 and ipv6 addresses.
Firefox attempts to connect via SOCKS proxy using ipv6 address
SOCKS proxy returns "Address type not supported" (status code 8)

Firefox does _nothing_. No error message, no apparent activity in browser.


Expected results:

Firefox should have reacted to this error by retrying the connection using an available ipv4 address, similar to what it presumably does if a regular unproxied TCP connection fails.

e.g.:
connect ipv6-addr ->
<- address type not supported
connect ipv4-addr ->

Comment 1

[Matthias Versen [:Matti]]

"network.proxy.socks_remote_dns" to "true" should fix this but you will get wrong error messages for NX Domains.
Another option is to disable IPv6 in Firefox.

Comment 2

[Julien ROBIN]

I confirm to have exacly the same problem : with my SSH Tunnel i'm now unable to browse a website which have an IPv6 adress. But there is completely no problems with websites that only have IPv4 adresses.

Firefox does nothing : research on google, click on a link... if there is an IPv6, nothing will be done.
This problem started as soon as I have my ISP configured to be IPv6 proof.

A perfect way to fix this problem could be to add a checkBox into the proxy configuration page, disable IPv6 for this proxy. Or to detect automatically the problem and switch to IPv4 when IPv6 returns an error.

Comment 3

[Julien ROBIN]

PS : I have spent a lot of time (months) to understand what was going on into my workplace, which already was IPv6 before I came to this company. I was completely unable to find why this problem, and how to make it disappear, because there is no message, nothing : it's a real bug that make Firefox staying completely unusable when we are trying to use the SSH Tunnel (with Putty) (without be aware of the cause of the problem) : I had to work with others Web Browsers !

Comment 4

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 5

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258