Its not unheard of for Windows 9x machines with no network card not to have a loopback on 127.0.0.1. ----- Original Message ----- From: "Edgar Friendly" <thel...@mh246001.truman.edu> To: <devl at freenetproject.org> Sent: Wednesday, January 02, 2002 5:33 AM Subject: Re: [freenet-devl] localhost handling errors (Windows)
> "Dave Hooper" <dave at beermex.com> writes: > > > Just dealing with a bug report for the Windows freenet control panel app and > > it appears that, for the user reporting the bug, whilst Internet Explorer > > can deal with both of the following, > > http://localhost:8888 > > http://127.0.0.1:8888 > > > > Netscape's browsers can only deal with the "localhost", and responds with a > > "Connection refused" for the 127.0.0.1 > > > That's the craziest thing I've ever heard of. I know my netscape > (well, mozilla, but same diff.) browser handles 127.0.0.1 just fine. > > > I have no experience of Netscape's browsers (I won't bother saying why not), > > so could anyone advise? Is Navigator unable to parse the local loopback > > address? Or could the user have accidentally done something mindlessly > > stupid (blocking 127.x.x.x for example) > > > > D > > > There's no reason that localhost and 127.x.x.x could possibly be > treated differently unless due to DNS they're resolving to different > IP addresses, and IE is short-cutting DNS when it looks up localhost. > > In any case, it's not a freenet problem, it's definitely some other > piece of this guy's system. > > Thelema > -- > E-mail: thelema314 at bigfoot.com Raabu and Piisu > GPG 1024D/36352AAB fpr:756D F615 B4F3 BFFC 02C7 84B7 D8D7 6ECE 3635 2AAB > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl > _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
