New: uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme
https://bugzilla.kernel.org/show_bug.cgi?id=215613
Bug ID: 215613
Summary: uri.7: DESCRIPTION: Usage: No description of the
'unix' URI scheme
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: [email protected]
Reporter: [email protected]
Regression: No
The subsection DESCRIPTION/Usage provides a description of common schemes in use on UNIX-like systems, but there's no mention of the 'unix:' scheme for Unix domain sockets.
AFAIK, it uses the same format as 'file:' (which is documented), but I don't know if there are any differences.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 215613] uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme
https://bugzilla.kernel.org/show_bug.cgi?id=215613
Thomas Piekarski ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Thomas Piekarski ([email protected]) --- I took a look into it and I have been unable to find any RFC for Unix domain socket URI schema for comparing if it is the same like file URI schema.
The IANA is not listing it [1].
The W3C is not listing it [2].
The RFC for Uniform Resource Locators [3] is not mentioning it nor does the RFC for file [4]. Well later was just a shot :-)
Maybe it is due to its nature for being used for inter-process communication, but from where such schema similar to internet schemas derive from?
The form is the same, but do unix://localhost/var/some-socket.sock accept such a form with localhost inside like file does? And do they behave the same in regards of file permissions?
---
[1]: https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
[2]: https://www.w3.org/wiki/UriSchemes
[3]: https://www.w3.org/Addressing/rfc1738.txt
[4]: https://www.rfc-editor.org/rfc/rfc8089.html
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.