From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] uri.7: Use "example.com" as example domain
Date: Sat, 8 Oct 2016 16:20:44 +0200 [thread overview]
Message-ID: <20161008142044.4983-1-jwilk@jwilk.net> (raw)
The owner of the "xyz.com" domain might not be happy that their domain
is used is examples. RFC 2606 reserves (among others) "example.com" for
this purpose, so let's use it.
Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
man7/uri.7 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man7/uri.7 b/man7/uri.7
index d1f20e5..4d3fc6a 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -124,8 +124,8 @@ The
is the name of the host computer, either its name as determined by DNS
or an IP address (numbers separated by periods).
Thus the URI
-<http://fred:fredpassword-+zpghU0kKgY@public.gmane.org:8080/>
-logs into a web server on host xyz.com
+<http://fred:fredpassword-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org:8080/>
+logs into a web server on host example.com
as fred (using fredpassword) using port 8080.
Avoid including a password in a URI if possible because of the many
security risks of having a password written down.
--
2.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-10-08 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 14:20 Jakub Wilk [this message]
[not found] ` <20161008142044.4983-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-10-08 18:07 ` [PATCH] uri.7: Use "example.com" as example domain Michael Kerrisk (man-pages)
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=20161008142044.4983-1-jwilk@jwilk.net \
--to=jwilk-txgolizoknreowh0uzbu5w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).