…s defined by [Berners-Lee et al.] , a work in progress expected to update [IETF RFC1738] and [IETF RFC1808] The list of known errors in this specification is available at Please report errors in this document to xml-editor@w3.org Extensible Markup Language (XML) 1.0 Table of Cont…
…]. This document obsoletes [RFC2396], which merged "Uniform Resource Locators" [RFC1738] and "Relative Uniform Resource Locators" [RFC1808] in order to define a single, generic syntax for all URIs. It obsoletes [RFC2732], which introduced syntax for an IPv6 address. It excludes p…
…al 13404 Dave_Thaler afs Andrew File System global file names Provisional 10687 RFC1738 aim prov/aim aim Provisional 10327 Dave_Thaler amss prov/amss amss Provisional 10831 RadioDNS_Project android prov/android android Provisional 15061 Adam_Barth ][ appdata prov/appdata appdata …
…This document obsoletes [ RFC2396 ], which merged "Uniform Resource Locators" [ RFC1738 ] and "Relative Uniform Resource Locators" RFC1808 ] in order to define a single, generic syntax for all URIs. It obsoletes [ RFC2732 ], which introduced syntax for an IPv6 address. It exclude…
…playable characters SHOULD be presented in URL %HH format defined in RFC 1738 [ RFC1738 ]. They MAY, however, display them as question marks, with their UCS hexadecimal value, or in any other suitable fashion. - Many existing clients interpret 8-bit pathnames as being in the loca…
…hemes for URIs. The first definition for many URI schemes appeared in RFC 1738 [RFC1738]. Because that document has been made obsolete, this document copies the gopher URI scheme from it to allow that material to remain on standards track. 2. Scheme Definition The gopher URL sche…
…splayable characters SHOULD be presented in URL %HH format defined in RFC 1738 [RFC1738]. They MAY, however, display them as question marks, with their UCS hexadecimal value, or in any other suitable fashion. - Many existing clients interpret 8-bit pathnames as being in the local…
…LOR, color) } . 3.7.2. The 'url' function URLs (Uniform Resource Locators, see [RFC1738] and [RFC1808] ) provide the address of a resource on the Web. An alternative and more general term is URIs (Uniform Resource Identifiers, see [!URI]). This specification uses the term URI. Fo…
…the rest of the URL. These characters are defined as unsafe in Section 2.2 of [ RFC1738 ]. Unsafe characters can result in unexpected behavior if they appear in the URL, for example, when the resource ID included in the path is a URL by itself, or in the search query string. The …
…body. 2 . Syntax of a mailto URL Following the syntax conventions of RFC 1738 [ RFC1738 ], a "mailto" URL has the form: Hoffman, et. al. Standards Track [Page 1] RFC 2368 The mailto URL scheme July 1998 mailtoURL = "mailto:" [ to ] [ headers ] to = #mailbox headers = "?" header *…
…emes for URIs. The first definition for many URI schemes appeared in RFC 1738 [ RFC1738 ]. Because that document has been made obsolete, this document copies the gopher URI scheme from it to allow that material to remain on standards track. 2 . Scheme Definition The gopher URL sc…
…splayable characters SHOULD be presented in URL %HH format defined in RFC 1738 [RFC1738]. They MAY, however, display them as question marks, with their UCS hexadecimal value, or in any other suitable fashion. - Many existing clients interpret 8-bit pathnames as being in the local…
…age body. . Syntax of a mailto URL Following the syntax conventions of RFC 1738 RFC1738 ], a "mailto" URL has the form: Hoffman, et. al. Standards Track [Page 1] RFC 2368 The mailto URL scheme July 1998 mailtoURL = "mailto:" [ to ] [ headers ] to = #mailbox headers = "?" header *…
…chemes for URIs. The first definition for many URI schemes appeared in RFC 1738 RFC1738 ]. Because that document has been made obsolete, this document copies the gopher URI scheme from it to allow that material to remain on standards track. . Scheme Definition The gopher URL sche…
…", 31 October 1996, T. Krauskopf, J. Miller, P. Resnick, W. Trees Available at [RFC1738] "Uniform Resource Locators", T. Berners-Lee, L. Masinter, and M. McCahill, December 1994. Available at ftp://ftp.isi.edu/in-notes/rfc1738.txt [RFC1766] "Tags for the Identification of Languag…