.\" (C) Copyright 1999-2000 David A. Wheeler (dwheeler@dwheeler.com)
.\"
-.\" %%%LICENSE_START(verbatim)
+.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\" Modified Fri Aug 21 23:00:00 1999 by David A. Wheeler (dwheeler@dwheeler.com)
.\" Modified Tue Mar 14 2000 by David A. Wheeler (dwheeler@dwheeler.com)
.\"
-.TH URI 7 2012-08-05 "Linux" "Linux Programmer's Manual"
+.TH URI 7 2017-09-15 "Linux" "Linux Programmer's Manual"
.SH NAME
uri, url, urn \- uniform resource identifier (URI), including a URL or URN
.SH SYNOPSIS
.PP
URIs are the standard way to name hypertext link destinations
for tools such as web browsers.
-The string "http://www.kernelnotes.org" is a URL (and thus it
+The string "http://www.kernel.org" is a URL (and thus it
is also a URI).
Many people use the term URL loosely as a synonym for URI
(though technically URLs are a subset of URIs).
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@xyz.com:8080/>
-logs into a web server on host xyz.com
+<http://fred:fredpassword@example.com: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.
.PP
This represents a file or directory accessible locally.
As a special case,
-.I host
+.I ip_server
can be the string "localhost" or the empty
string; this is interpreted as "the machine from which the URL is
being interpreted".
.PP
Unreserved characters may be included in a URI.
Unreserved characters
-include upper and lower case English letters,
+include uppercase and lowercase English letters,
decimal digits, and the following
limited set of punctuation marks and symbols:
.IP
All other characters must be escaped.
An escaped octet is encoded as a character triplet, consisting of the
percent character "%" followed by the two hexadecimal digits
-representing the octet code (you can use upper or lower case letters
+representing the octet code (you can use uppercase or lowercase letters
for the hexadecimal digits).
For example, a blank space must be escaped
as "%20", a tab character as "%09", and the "&" as "%26".
use the %HH encoding for unsafe octets.
.SS Writing a URI
When written, URIs should be placed inside double quotes
-(e.g., "http://www.kernelnotes.org"),
+(e.g., "http://www.kernel.org"),
enclosed in angle brackets (e.g., <http://lwn.net>),
or placed on a line by themselves.
A warning for those who use double-quotes:
change over time, particularly when new schemes are introduced.
Since an abbreviated URI has the same syntax as a relative URL path,
abbreviated URI references cannot be used where relative URIs are
-permitted, and can only be used when there is no defined base
+permitted, and can be used only when there is no defined base
(such as in dialog boxes).
Don't use abbreviated URIs as hypertext links inside a document;
use the standard format as described here.
.UR http://www.ietf.org\:/rfc\:/rfc2396.txt
(IETF RFC\ 2396)
.UE ,
-.UR http://www.w3.org\:/TR\:/REC-html40
+.UR http://www.w3.org\:/TR\:/REC\-html40
(HTML 4.0)
.UE .
.SH NOTES
located a given resource, will continue to do so.
Nor is there any
guarantee that a URL will not locate a different resource at some
-later point in time; such a guarantee can only be
-obtained from the person(s) controlling that namespace and the
+later point in time; such a guarantee can be
+obtained only from the person(s) controlling that namespace and the
resource in question.
.PP
It is sometimes possible to construct a URL such that an attempt to
(though filename globbing could partially overcome this).
Finally, using the file: scheme doesn't easily support people
who dynamically load documentation from the Internet (instead of
-loading the files onto a local file system).
+loading the files onto a local filesystem).
A future URI scheme may be added (e.g., "userdoc:") to permit
programs to include cross-references to more detailed documentation
without having to know the exact location of that documentation.
-Alternatively, a future version of the file-system specification may
+Alternatively, a future version of the filesystem specification may
specify file locations sufficiently so that the file: scheme will
be able to locate documentation.
.PP
.BR man2html (1),
.BR mailaddr (7),
.BR utf-8 (7)
-
+.PP
.UR http://www.ietf.org\:/rfc\:/rfc2255.txt
IETF RFC\ 2255
.UE