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

What about

```
    http://host.example.com.uds.localhost/path/to/socket//path/to/resource
    https://host.example.com.uds.localhost/path/to/socket//path/to/resource
```
An HTTP client library would strip .uds.localhost from the host portion and pass the remainder in the host header (and SNI, if using TLS). I think most URL parsers would be happy with this. localhost is a reserved toplevel domain (RFC 2606) so this won't ever conflict with a real hostname. And it doesn't require introducing new schemes, or any new syntax (such as hijacking the port number field).

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

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