Closed
Bug 266534
Opened 20 years ago
Closed 20 years ago
Fall back to IPv4 on IPv6 error doesn't always work
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 246193
People
(Reporter: mozillabugzilla, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
I have 2 machines on which IPv6 is (differently) misconfigured. On one of them,
firefox falls back correctly from IPv6 to IPv4, on the other one it doesn't.
On the machine where it falls back correctly, connect() for IPv6 fails with
'Network is unreachable'. On the machine where it doesn't fall back, connect()
for IPv6 gives 'Cannot assign requested address'.
Where it doesn't seem to fall back, the location bar shows the url I wanted to
reach, but the content page doesn't change and shows the previous page. The
favicon icon is reset to the default page icon though.
I'd like to give a more detailed report, but don't know how to get more specific
information on why this is malfunctioning. I'm quite prepared to run any tests
you might propose.
As a side note, looking at ethereal shows that mozilla does do both an A and
AAAA DNS request, but doesn't seem to make a connection to the returned addresses.
Reproducible: Always
Steps to Reproduce:
0. Go to a page with a custom 'favicon'
1. Make sure your computer is malconfigured in such a way that connect() for an
IPv6 connection returns 'Cannot assign requested address'
2. Type in an URL for which both an A and AAAA record exist.
Actual Results:
the page doesn't change, but the favicon is reset and the location bar is set to
the URL where we wanted to go
Expected Results:
When the IPv6 connection failed, an IPv4 connection should've been made and the
page should've been loaded.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 246193 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•