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
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
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl