Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)

@PHJArea217
> @randomstuff's "soxidier" tool maps domain names to unix domain sockets, such that if the user went to http://name.username.users.uds.localhost/foo/bar then it would be effectively connecting to e.g. /home/username/name, and making the request GET /foo/bar HTTP/1.1, with the possibility of using symlinks to redirect connections to other sockets outside of this pattern.

Well, fine.  But, as I said, that is not an RFC 3986 compliant URI.

A list of IANA recognized top-level Domain Names can be found at: https://data.iana.org/TLD/tlds-alpha-by-domain.txt 
"localhost" is not on that list.

Of course, you could configure your own local dns server to resolve "localhost" to some server on your local network, but that is not a general solution.  It would be useless for accessing a host on the global Internet.

To be clear, with respect to the solution which I have proposed, the pros and cons come down to a question of a single ":" character.  Seriously - the placement of a single ":" character in the context of the entire RFC 3986.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/577#issuecomment-2606349163
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/577/2606349163@github.com>