Steven Allen
Steven Allen
* Some browsers (should include firefox and chrome?) will automatically resolve *.localhost domains internally. What browser are you using? * Are you using a local DNS resolver? Most (including systemd-resolved)...
Ah, I see... we discussed special-casing curl and just not redirecting for curl. Note: `curl` without `-L` should still magically work, but your solution of `nss-myhostname` is definitely a better...
I've filed https://github.com/ipfs/go-ipfs/issues/7293 to summarize this issue. LGTY?
@lidel has the browser story changed here?
Nothing has changed here, unfortunately.
Closing as something we'll have to re-evaluate for a 1.0 release.
So, one solution is "do both". That is: try to listen on mulitple ports but succeed if at least one of the listen addresses succeeds.
Having the default port change over night is likely even worse. I'd like to give users a transition period.
That will work for IPv4, but not ipv6.
Hm. Although I guess we don't even listen on IPv6 by default.