Closed
Bug 680466
Opened 13 years ago
Closed 13 years ago
Firefox 9 prefers ipv4 and not ipv6
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 679090
People
(Reporter: bug-mozilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0a1) Gecko/20110819 Firefox/9.0a1 Build ID: 20110819030749 Steps to reproduce: I was on the Web site http://test-ipv6.com/ which makes it possible to test its connection ipv6. OS : Windows 7 64 bits - Connection Dual Stack IPV4-IPV6 Actual results: In the test, the first time Firefox 9 prefers IPV4 and the second time, it prefers IPV6. Expected results: Firefox should prefer IPV6 in permanence and not in a random way. Firefox 6 release does not have this problem, it always prefers IPV6.
Comment 2•13 years ago
|
||
That's because of bug 621558 - If IPv4 doesn't respond in 250 ms, IPv4 is tried as a quick fallback. See also <http://tools.ietf.org/html/draft-wing-http-new-tech-00>
Comment 3•13 years ago
|
||
Jo meant "If IPv6 doesn't respond in 250 ms, IPv4 is tried as a quick fallback". I can confirm that IPv6 works fine if the IPv6 connection is fast enough. Is your IPv6 connection to http://test-ipv6.com/ slower as 250ms ?
Reporter | ||
Comment 4•13 years ago
|
||
My connection IPV6 towards http://test-ipv6.com/ is of 207ms. I made the test on Firefox 8 Aurora and Firefox 7 Beta, the first time they prefer IPV4 and as of I reactualize the page, they prefer IPV6. I carried out this test on various navigators IE 9, Opéra 11.50, Safari 5.1, Chrome 13, they prefer all IPV6 as of the first time. This operating mode of the new versions of Firefox poses problem on Web sites which identifies you by your IPV6 static with login and password, if it detects a change of IP in course of consultation of the site, they refuse you the access. One would need an option in Firefox for preferred IPV6 in permanence and not only by detection of the latency time.
Updated•13 years ago
|
Component: General → Networking: HTTP
Product: Firefox → Core
QA Contact: general → networking.http
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•