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

> Just wanted to chime in here with my own opinion on this.
> 
> Unix domain sockets are an OS-specific transport. Windows has named pipes instead. Due to their local nature, simply embedding the Unix socket path or named pipe path would result in two different and somewhat incompatible representations for applications which must work on both Windows and Unix-like systems.

All of this is orthogonal to the problem, which is we need a standardised way to express an http(s) URL that points to a unix domain socket. There is no reason why an arbitrary (and legacy) difference between two arbitrary operating systems should place a limit on a standard like an URL definition.

Other types of sockets on other platforms are discussions that should go under a separate issue.


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

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