Closed
Bug 66749
Opened 24 years ago
Closed 24 years ago
Can't find the localhost when a IP v6 id is in localhost
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: dieter.landolt, Assigned: neeti)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16 i686; en-US; 0.7) Gecko/20010105 BuildID: 2001010517 If you have 2 lines in yout /etc/hosts file, one witch is as folow : 127.0.0.1 localhost an a little later the folow ::1 localhost ipv6-localhost ipv6-loopback your bowser is not able to look up. It try's all ways to get the IP'v 6 way but its not able. Reproducible: Always Steps to Reproduce: Put this two lines in zhis order in your /etc/hosts file. 127.0.0.1 localhost ::1 localhost ipv6-localhost ipv6-loopback then try to get a http site from a local host like http://localhost. Actual Results: Not able to find the host. Expected Results: i think you schould use the standard lookup calls in the operation system, insted of direct look up in the /etc/hosts table. But i don't now how you make it at the time. If you try it with netscape 4.76 you will not get this problem. In some reasons you ar able to delete the ip V6 line. In moste case you will not need it.
Updated•24 years ago
|
Assignee: asa → neeti
Component: Browser-General → Networking
QA Contact: doronr → tever
Comment 1•24 years ago
|
||
Works for me with 01/22 CVS build on Linux, but I have a local nameserver running. Besides, the default configuration on my system (Debian Woody) is: 127.0.0.1 localhost ::1 ipv6-localhost ipv6-loopback Wouldn't that be enough? (Over to Networking.)
Comment 2•24 years ago
|
||
There is a slightly newer bug on this issue that has a slightly clearer description of what the problem is behind the scenes. Marking as duplicate. Thanks for using Mozilla and reporting bugs, and especially for writing clear and easy to understand bug reports! *** This bug has been marked as a duplicate of 66872 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•