On 3 December 2012 22:54, Erik Leunissen <[email protected]> wrote: > L.S. > > When doing [fossil ui] on my system[*], I get the HTTP error: > > Firefox can't establish a connection to the server at localhost:8080 > > The reason for this is probably that the client attempts to connect to > localhost, while the server is listening at (a hard coded?) 127.0.0.1. > > I think so because the connection succeeds when I separately launch the > service using [fossil server], and next make the browser connect to > 127.0.0.1. > > So there is an issue with the interpretation of the hostname "localhost". On > my system, localhost resolves as ::1, which is not 127.0.0.1. That explains > the connection failure. > > If so, the solution would be to make client and server interpret the name > "localhost" in the same way. Or refrain from using "localhost" at all, and > use 127.0.0.1 at both sides, but then you will get issues at the time when > IPv4 is completely deprecated.
Localhost should resolve to both ::1 and 127.0.0.1 on dual-stack systems. Programs using a name instead of an address are supposed to try all the addresses they get for the name in some order until they find one which works. If your order is wrong, and your program is using TCP, you may get long waits for TCP connect timeouts. -- Christopher Vance _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
