- From: Klaus Frank <notifications@github.com>
- Date: Wed, 13 Jul 2022 15:04:32 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 July 2022 22:04:45 UTC
(@thx1111 ":/" would be a valid filename on jfs...) I think there are only two acceptable solutions: * Using an adoption of the IPvFuture syntax from RFC3986 Section 3.2.2 like @cyanogilvie already mentioned `http://[v1.uds:/tmp/mysock]/foo/bar` * A syntax similar to: `http+unix:///path/to/socket//resource/path`, where "+unix" is a modifier for the url schema that specifies a different parsing schema. As it could be applied to any protocol not just http, like ftp, https, gopher, ... and the double slash is the delimiter between file url and resource path. But this also has issues with crossplatform compatibility, as windows has different syntax (ok, one could write `C:/path/to/file` and it would work, but that's not the default what everyone expects) https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/577#issuecomment-1183724217 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/577/1183724217@github.com>
Received on Wednesday, 13 July 2022 22:04:45 UTC