From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215613] uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme
Date: Thu, 17 Feb 2022 20:55:09 +0000 [thread overview]
Message-ID: <bug-215613-11311-scIof60VEp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215613-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215613
Thomas Piekarski (t.piekarski@deloquencia.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t.piekarski@deloquencia.de
--- Comment #1 from Thomas Piekarski (t.piekarski@deloquencia.de) ---
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
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-02-17 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 15:31 [Bug 215613] New: uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme bugzilla-daemon
2022-02-17 20:55 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215613-11311-scIof60VEp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox