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

Reading back through this discussion, it has not at all been established that there is a consensus as to "where" the underlying issue *should* lie, and so, any "solution" offered can appear to simply "miss the point", depending upon your point of view.  I find myself back-and-forth about the various approaches suggested, including my own.

I can summarize least four alternatives proposed here to the issue of, to generalize, "Addressing Unix Domain Sockets".

1) RFC 3986 "Uniform Resource Identifier (URI): Generic Syntax" must be modified to allow addressing unix domain sockets.

2) The URI Shemes in BCP 35/RFC 7595 "Guidelines and Registration Procedures for URI Schemes" must define a new URI Scheme and Owner which specifically supports unix domain socket addressing.
Review here: https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml

3) The existing http/https schemes defined in RFC 8615 "Well-Known Uniform Resource Identifiers (URIs)" must be expanded to explicitly support addressing unix domain sockets.

4) Ignore the URI standard RFCs and just write or modify an html display client to support unix domain socket addressing.

Without first saying which approach we are thinking about, the conversation can become kind of silly, since any solution which "works", works.  Otherwise, it may be that I both enjoy, and cringe at, "bike shedding" as much as anyone else.

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

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