URL

<h2 id="history">History</h2>
Uniform Resource Locators were defined in <a href="/facts/RFC_(identifier)/esftTvE7">RFC</a> <a href="https://www.rfc-editor.org/rfc/rfc1738">1738</a> in 1994 by <a href="/facts/Tim_Berners-Lee/JRv21mt9">Tim Berners-Lee</a>, the inventor of the <a href="/facts/World_Wide_Web/wvnTrWFq">World Wide Web</a>, and the URI working group of the <a href="/facts/Internet_Engineering_Task_Force/tIcCsFhX">Internet Engineering Task Force</a> (IETF),<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a> as an outcome of collaboration started at the IETF Living Documents <a href="/facts/Birds_of_a_feather_(computing)/tIcCsFhX">birds of a feather</a> session in 1992.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a><a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>
The format combines the pre-existing system of <a href="/facts/Domain_name/FDLD2m5G">domain names</a> (created in 1985) with <a href="/facts/Path_(computing)/F5wNAuMY">file path</a> syntax, where <a href="/facts/Slash_(punctuation)/fuaRyKzc">slashes</a> are used to separate <a href="/facts/Folder_(computing)/VLtLcEXY">directory</a> and <a href="/facts/Filename/EGc4tA7n">filenames</a>. Conventions already existed where server names could be prefixed to complete file paths, preceded by a double slash (//).<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a>
Berners-Lee later expressed regret at the use of dots to separate the parts of the <a href="/facts/Domain_name/FDLD2m5G">domain name</a> within <a href="/facts/URI/UjyqxTpA">URIs</a>, wishing he had used slashes throughout,<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a> and also said that, given the colon following the first component of a URI, the two slashes before the domain name were unnecessary.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a>
Early <a href="/facts/WorldWideWeb/FlgLKla7">WorldWideWeb</a> collaborators including Berners-Lee originally proposed the use of UDIs: Universal Document Identifiers.
An early (1993) draft of the HTML Specification<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a> referred to "Universal" Resource Locators. This was dropped some time between June 1994 (RFC <a href="https://www.rfc-editor.org/rfc/rfc1630">1630</a>) and October 1994 (draft-ietf-uri-url-08.txt).<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a> In his book <a href="/facts/Weaving_the_Web/evgDM2Jv">Weaving the Web</a>, Berners-Lee emphasizes his preference for the original inclusion of "universal" in the expansion rather than the word "uniform", to which it was later changed, and he gives a brief account of the contention that led to the change.

<h2 id="syntax">Syntax</h2>
Main article: <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">Uniform Resource Identifier § Syntax</a>
Every HTTP URL conforms to the syntax of a generic URI. The URI generic syntax consists of five components organized hierarchically in order of decreasing significance from left to right:<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a>: §3 

URI = scheme ":" ["//" authority] path ["?" query] ["#" fragment]

A component is undefined if it has an associated delimiter and the delimiter does not appear in the URI; the scheme and path components are always defined.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>: §5.2.1  A component is empty if it has no characters; the scheme component is always non-empty.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>: §3 
The authority component consists of subcomponents:

authority = [userinfo "@"] host [":" port]

This is represented in a <a href="/facts/Syntax_diagram/NdvSrCKb">syntax diagram</a> as:

The URI comprises:

<ul><li>A non-empty scheme component followed by a colon (:), consisting of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus (+), period (.), or hyphen (-). Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. Examples of popular schemes include <a href="/facts/Hypertext_Transfer_Protocol/TWtvf7JD">http</a>, <a href="/facts/HTTP_Secure/MSWYz4zo">https</a>, <a href="/facts/File_Transfer_Protocol/THuWgzfw">ftp</a>, <a href="/facts/Mailto/zF0frput">mailto</a>, <a href="/facts/File_URI_scheme/tF8tPGzK">file</a>, <a href="/facts/Data_URI_scheme/7hBR45J2">data</a> and <a href="/facts/Internet_Relay_Chat/oDr3VN9q">irc</a>. URI schemes should be registered with the <a href="/facts/Internet_Assigned_Numbers_Authority/b6MlP6zQ">Internet Assigned Numbers Authority (IANA)</a>, although non-registered schemes are used in practice.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a></li>
<li>An optional authority component preceded by two slashes (//), comprising:
<ul><li>An optional userinfo subcomponent followed by an at symbol (@), that may consist of a <a href="/facts/User_(computing)/zQRzG0KG">user name</a> and an optional <a href="/facts/Password/WEoul230">password</a> preceded by a colon (:). Use of the format username:password in the userinfo subcomponent is deprecated for security reasons. Applications should not render as clear text any data after the first colon (:) found within a userinfo subcomponent unless the data after the colon is the empty string (indicating no password).</li>
<li>A host subcomponent, consisting of either a registered name (including but not limited to a <a href="/facts/Hostname/WcLyMFKA">hostname</a>) or an <a href="/facts/IP_address/z9V22Sw9">IP address</a>. <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> addresses must be in <a href="/facts/Dot-decimal_notation/Tea5wKCB">dot-decimal notation</a>, and <a href="/facts/IPv6/d4dg7kIL">IPv6</a> addresses must be enclosed in brackets ([]).<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a>: §3.2.2 <a class="footnote-ref" id="fnref:19" href="#fn:19">19</a></li>
<li>An optional port subcomponent preceded by a colon (:), consisting of decimal digits.</li></ul></li>
<li>A path component, consisting of a sequence of path segments separated by a slash (/). A path is always defined for a URI, though the defined path may be empty (zero length). A segment may also be empty, resulting in two consecutive slashes (//) in the path component. A path component may resemble or map exactly to a <a href="/facts/Path_(computing)/F5wNAuMY">file system path</a> but does not always imply a relation to one. If an authority component is defined, then the path component must either be empty or begin with a slash (/). If an authority component is undefined, then the path cannot begin with an empty segment—that is, with two slashes (//)—since the following characters would be interpreted as an authority component.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a>: §3.3 </li></ul>
By convention, in http and https URIs, the last part of a path is named pathinfo and it is optional. It is composed by zero or more path segments that do not refer to an existing physical resource name (e.g. a file, an internal module program or an executable program) but to a logical part (e.g. a command or a qualifier part) that has to be passed separately to the first part of the path that identifies an executable module or program managed by a <a href="/facts/Web_server/A4GS6thA">web server</a>; this is often used to select dynamic content (a document, etc.) or to tailor it as requested (see also: <a href="/facts/Common_Gateway_Interface/zWsLFXGJ">CGI</a> and PATH_INFO, etc.).
Example:
URI: "http://www.example.com/questions/3456/my-document"
where: "/questions" is the first part of the path (an executable module or program) and "/3456/my-document" is the second part of the path named pathinfo, which is passed to the executable module or program named "/questions" to select the requested document.
An http or https URI containing a pathinfo part without a query part may also be referred to as a '<a href="/facts/Clean_URL/zqJIfg7q">clean URL</a>,' whose last part may be a '<a href="/facts/Clean_URL/zqJIfg7q">slug</a>.'
<table><tbody><tr><th>Query delimiter</th><th>Example</th></tr><tr><td>Ampersand (&)</td><td>key1=value1&key2=value2</td></tr><tr><td>Semicolon (;)<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a></td><td>key1=value1;key2=value2</td></tr></tbody></table>
<ul><li>An optional query component preceded by a question mark (?), consisting of a <a href="/facts/Query_string/nUTW9ITa">query string</a> of non-hierarchical data. Its syntax is not well defined, but by convention is most often a sequence of <a href="/facts/Attribute%25E2%2580%2593value_pair/buweLY96">attribute–value pairs</a> separated by a <a href="/facts/Delimiter/wRAQxIKV">delimiter</a>.</li>
<li>An optional fragment component preceded by a <a href="/facts/Number_sign/bHYCsWs1">hash</a> (#). The fragment contains a <a href="/facts/Fragment_identifier/lbA3Apwq">fragment identifier</a> providing direction to a secondary resource, such as a section heading in an article identified by the remainder of the URI. When the primary resource is an <a href="/facts/HTML/sSc3fT78">HTML</a> document, the fragment is often an <a href="/facts/HTML/sSc3fT78">id attribute</a> of a specific element, and web browsers will scroll this element into view.</li></ul>
A web browser will usually <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">dereference</a> a URL by performing an <a href="/facts/Hypertext_Transfer_Protocol/TWtvf7JD">HTTP</a> request to the specified host, by default on port number 80. URLs using the https scheme require that requests and responses be made over a <a href="/facts/HTTPS/MSWYz4zo">secure connection to the website</a>.

<h2 id="internationalized-url">Internationalized URL</h2>
Internet users are distributed throughout the world using a wide variety of languages and alphabets, and expect to be able to create URLs in their own local alphabets. An <a href="/facts/Internationalized_Resource_Identifier/x3JWG8Gx">Internationalized Resource Identifier</a> (IRI) is a form of URL that includes <a href="/facts/Unicode/DDu3MfPV">Unicode</a> characters. All modern browsers support IRIs. The parts of the URL requiring special treatment for different alphabets are the domain name and path.<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a><a class="footnote-ref" id="fnref:23" href="#fn:23">23</a>
The domain name in the IRI is known as an <a href="/facts/Internationalized_Domain_Name/nbaJweyM">Internationalized Domain Name</a> (IDN). Web and Internet software automatically convert the domain name into <a href="/facts/Punycode/tolxnMjr">punycode</a> usable by the <a href="/facts/Domain_Name_System/rfxdWFsj">Domain Name System</a>; for example, the Chinese URL http://例子.卷筒纸 becomes http://xn--fsqu00a.xn--3lr804guic/. The xn-- indicates that the character was not originally <a href="/facts/ASCII/vGUI33Qu">ASCII</a>.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a>
The URL path name can also be specified by the user in the local writing system. If not already encoded, it is converted to <a href="/facts/UTF-8/xlaVHSyf">UTF-8</a>, and any characters not part of the basic URL character set are escaped as <a href="/facts/Hexadecimal/02ohQW22">hexadecimal</a> using <a href="/facts/Percent-encoding/zprLw5se">percent-encoding</a>; for example, the Japanese URL http://example.com/引き割り.html becomes http://example.com/%E5%BC%95%E3%81%8D%E5%89%B2%E3%82%8A.html. The target computer decodes the address and displays the page.<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a>

<h2 id="protocol-relative-urls">Protocol-relative URLs</h2>
Protocol-relative links (PRL), also known as protocol-relative URLs (PRURL), are URLs that have no protocol specified. For example, //example.com will use the protocol of the current page, typically HTTP or HTTPS.<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a><a class="footnote-ref" id="fnref:27" href="#fn:27">27</a>

<h2 id="see-also">See also</h2>

<ul><li><a href="/facts/Hyperlink/LqNsa84e">Hyperlink</a></li>
<li><a href="/facts/Persistent_uniform_resource_locator/KKYhANhT">PURL</a> – Persistent URL</li>
<li><a href="/facts/CURIE/yfR66xgD">CURIE</a> (Compact URI)</li>
<li><a href="/facts/URI_fragment/lbA3Apwq">URI fragment</a></li>
<li><a href="/facts/Internet_resource_locator/ChUWjQ6s">Internet resource locator</a> (IRL)</li>
<li><a href="/facts/Internationalized_Resource_Identifier/x3JWG8Gx">Internationalized Resource Identifier</a> (IRI)</li>
<li><a href="/facts/Clean_URL/zqJIfg7q">Clean URL</a></li>
<li><a href="/facts/Typosquatting/NjU7pBI1">Typosquatting</a></li>
<li><a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">Uniform Resource Identifier</a></li>
<li><a href="/facts/URI_normalization/wUyUTo9R">URI normalization</a></li>
<li><a href="/facts/Slash_(punctuation)/fuaRyKzc">Use of slashes in networking</a></li></ul>

<h2 id="notes">Notes</h2>

<h2 id="citations">Citations</h2>

<ul><li><a href="http://news.bbc.co.uk/1/hi/technology/8306631.stm">"Berners-Lee "sorry" for slashes"</a>. <a href="/facts/BBC_News/oGAe2H8E">BBC News</a>. 2009-10-14. <a href="https://web.archive.org/web/20200605102245/http://news.bbc.co.uk/2/hi/technology/8306631.stm">Archived</a> from the original on 2020-06-05. Retrieved 2010-02-14.</li>
<li><a href="http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html">"Living Documents BoF Minutes"</a>. <a href="/facts/World_Wide_Web_Consortium/lGWmhF6M">World Wide Web Consortium</a>. 1992-03-18. <a href="https://web.archive.org/web/20121122075812/http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html">Archived</a> from the original on 2012-11-22. Retrieved 2011-12-26.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a> (1994-03-21). <a href="http://www.w3.org/Addressing/URL/url-spec.txt">"Uniform Resource Locators (URL): A Syntax for the Expression of Access Information of Objects on the Network"</a>. <a href="/facts/World_Wide_Web_Consortium/lGWmhF6M">World Wide Web Consortium</a>. <a href="https://web.archive.org/web/20150909152849/http://www.w3.org/Addressing/URL/url-spec.txt">Archived</a> from the original on 2015-09-09. Retrieved 2015-09-13.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a>; <a href="/facts/Larry_Masinter/GuKjgjhB">Masinter, Larry</a>; <a href="/facts/Mark_Perry_McCahill/mR944N48">McCahill, Mark Perry</a> (December 1994). <a href="https://datatracker.ietf.org/doc/html/rfc1738">Uniform Resource Locators (URL)</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC1738">10.17487/RFC1738</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc1738">1738</a>. Retrieved 2015-08-31.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a> (2015) [2000]. <a href="http://www.w3.org/People/Berners-Lee/FAQ.html#etc">"Why the //, #, etc?"</a>. Frequently asked questions. <a href="/facts/World_Wide_Web_Consortium/lGWmhF6M">World Wide Web Consortium</a>. <a href="https://web.archive.org/web/20200514191316/https://www.w3.org/People/Berners-Lee/FAQ.html#etc">Archived</a> from the original on 2020-05-14. Retrieved 2010-02-03.</li>
<li><a href="/facts/Daniel_Connolly_(computer_scientist)/kMtjty64">Connolly, Daniel "Dan"</a>; <a href="/facts/C._Michael_Sperberg-McQueen/u0bR2XDN">Sperberg-McQueen, C. Michael</a>, eds. (2009-05-21). <a href="http://www.w3.org/html/wg/href/draft#url">"Web addresses in HTML 5"</a>. <a href="/facts/World_Wide_Web_Consortium/lGWmhF6M">World Wide Web Consortium</a>. <a href="https://web.archive.org/web/20150710151425/http://www.w3.org/html/wg/href/draft#url">Archived</a> from the original on 2015-07-10. Retrieved 2015-09-13.</li>
<li><a href="/facts/Internet_Assigned_Numbers_Authority/b6MlP6zQ">IANA</a> (2003-02-14). <a href="https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html">"Completion of IANA Selection of IDNA Prefix"</a>. IETF-Announce mailing list. Archived from <a href="http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html">the original</a> on 2004-12-08. Retrieved 2015-09-03.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a>; <a href="/facts/Daniel_Connolly_(computer_scientist)/kMtjty64">Connolly, Daniel "Dan"</a> (November 1995). <a href="https://datatracker.ietf.org/doc/html/rfc1866#section-8.2.1">"Hypertext Markup Language – 2.0"</a>. IETF Datatracker. <a href="/facts/Internet_Engineering_Task_Force/tIcCsFhX">Internet Engineering Task Force</a>. sec. 8.2.1. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC1866">10.17487/RFC1866</a>. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:6628570">6628570</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc1866">1866</a>. Retrieved 2015-09-13.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a>; <a href="/facts/Roy_T._Fielding/Arp1Qy5X">Fielding, Roy T.</a>; <a href="/facts/Larry_Masinter/GuKjgjhB">Masinter, Larry</a> (August 1998). <a href="https://datatracker.ietf.org/doc/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC2396">10.17487/RFC2396</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc2396">2396</a>. Retrieved 2015-08-31.</li>
<li>Hansen, Tony; Hardie, Ted (June 2015). Thaler, Dave (ed.). <a href="https://datatracker.ietf.org/doc/html/rfc7595">Guidelines and Registration Procedures for URI Schemes</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC7595">10.17487/RFC7595</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc7595">7595</a>.</li>
<li><a href="/facts/Michael_Mealling/VmfVdjJV">Mealling, Michael</a>; Denenberg, Ray, eds. (August 2002). <a href="https://datatracker.ietf.org/doc/html/rfc3305">Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC3305">10.17487/RFC3305</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc3305">3305</a>. Retrieved 2015-09-13.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a>; <a href="/facts/Roy_T._Fielding/Arp1Qy5X">Fielding, Roy T.</a>; <a href="/facts/Larry_Masinter/GuKjgjhB">Masinter, Larry</a> (January 2005). <a href="https://datatracker.ietf.org/doc/html/rfc3986">Uniform Resource Identifiers (URI): Generic Syntax</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC3986">10.17487/RFC3986</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc3986">3986</a>. Retrieved 2015-08-31.</li>
<li><a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee, Tim</a>; <a href="/facts/Roy_T._Fielding/Arp1Qy5X">Fielding, Roy T.</a>; <a href="/facts/Larry_Masinter/GuKjgjhB">Masinter, Larry</a> (January 2005). <a href="https://datatracker.ietf.org/doc/html/rfc3986#section-3">"Syntax Components"</a>. <a href="https://datatracker.ietf.org/doc/html/rfc3986">Uniform Resource Identifiers (URI): Generic Syntax</a>. sec. 3. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC3986">10.17487/RFC3986</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc3986">3986</a>. Retrieved 2015-08-31.</li>
<li><a href="http://www.w3.org/International/articles/idn-and-iri/">"An Introduction to Multilingual Web Addresses"</a>. 2008-05-09. <a href="https://web.archive.org/web/20150105041451/http://www.w3.org/International/articles/idn-and-iri/">Archived</a> from the original on 2015-01-05. Retrieved 2015-01-11.</li>
<li>Phillip, A. (2014). <a href="https://www.w3.org/International/wiki/IRIStatus">"What is Happening with "International URLs""</a>. <a href="/facts/World_Wide_Web_Consortium/lGWmhF6M">World Wide Web Consortium</a>. <a href="https://web.archive.org/web/20150217192459/https://www.w3.org/International/wiki/IRIStatus">Archived</a> from the original on 2015-02-17. Retrieved 2015-01-11.</li>
<li>Lawrence, Eric (2014-03-06). <a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls">"Browser Arcana: IP Literals in URLs"</a>. Microsoft Learn. <a href="https://web.archive.org/web/20200622181648/https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls">Archived</a> from the original on 2020-06-22. Retrieved 2020-06-22.</li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="https://url.spec.whatwg.org/">URL specification</a> at <a href="/facts/WHATWG/WoyKwRJR">WHATWG</a></li>
<li><a href="https://slevithan.github.io/parseuri/demo/">URL splitter</a> that splits any URI into its parts</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">W3C (2009). - Connolly, Daniel "Dan"; Sperberg-McQueen, C. Michael, eds. (2009-05-21). "Web addresses in HTML 5". World Wide Web Consortium. Archived from the original on 2015-07-10. Retrieved 2015-09-13. <a href="http://www.w3.org/html/wg/href/draft#url" target="_blank">http://www.w3.org/html/wg/href/draft#url</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">"Forward and Backslashes in URLs". zzz.buzz. Archived from the original on 2018-09-04. Retrieved 2018-09-19. <a href="https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/" target="_blank">https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">RFC 3986 (2005). - Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry (January 2005). Uniform Resource Identifiers (URI): Generic Syntax. doi:10.17487/RFC3986. RFC 3986. Retrieved 2015-08-31. <a href="https://datatracker.ietf.org/doc/html/rfc3986" target="_blank">https://datatracker.ietf.org/doc/html/rfc3986</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Joint W3C/IETF URI Planning Interest Group (2002). - Mealling, Michael; Denenberg, Ray, eds. (August 2002). Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations. doi:10.17487/RFC3305. RFC 3305. Retrieved 2015-09-13. <a href="https://datatracker.ietf.org/doc/html/rfc3305" target="_blank">https://datatracker.ietf.org/doc/html/rfc3305</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">A URL implies the means to access an indicated resource and is denoted by a protocol or an access mechanism, which is not true of every URI.[5][4] Thus http://www.example.com is a URL, while www.example.com is not.[6] <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">W3C (1994). - Berners-Lee, Tim (1994-03-21). "Uniform Resource Locators (URL): A Syntax for the Expression of Access Information of Objects on the Network". World Wide Web Consortium. Archived from the original on 2015-09-09. Retrieved 2015-09-13. <a href="http://www.w3.org/Addressing/URL/url-spec.txt" target="_blank">http://www.w3.org/Addressing/URL/url-spec.txt</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">W3C (1994). - Berners-Lee, Tim (1994-03-21). "Uniform Resource Locators (URL): A Syntax for the Expression of Access Information of Objects on the Network". World Wide Web Consortium. Archived from the original on 2015-09-09. Retrieved 2015-09-13. <a href="http://www.w3.org/Addressing/URL/url-spec.txt" target="_blank">http://www.w3.org/Addressing/URL/url-spec.txt</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">IETF (1992). - "Living Documents BoF Minutes". World Wide Web Consortium. 1992-03-18. Archived from the original on 2012-11-22. Retrieved 2011-12-26. <a href="http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html" target="_blank">http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">Berners-Lee (2015). - Berners-Lee, Tim (2015) [2000]. "Why the //, #, etc?". Frequently asked questions. World Wide Web Consortium. Archived from the original on 2020-05-14. Retrieved 2010-02-03. <a href="http://www.w3.org/People/Berners-Lee/FAQ.html#etc" target="_blank">http://www.w3.org/People/Berners-Lee/FAQ.html#etc</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Berners-Lee (2015). - Berners-Lee, Tim (2015) [2000]. "Why the //, #, etc?". Frequently asked questions. World Wide Web Consortium. Archived from the original on 2020-05-14. Retrieved 2010-02-03. <a href="http://www.w3.org/People/Berners-Lee/FAQ.html#etc" target="_blank">http://www.w3.org/People/Berners-Lee/FAQ.html#etc</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">BBC News (2009). - "Berners-Lee "sorry" for slashes". BBC News. 2009-10-14. Archived from the original on 2020-06-05. Retrieved 2010-02-14. <a href="http://news.bbc.co.uk/1/hi/technology/8306631.stm" target="_blank">http://news.bbc.co.uk/1/hi/technology/8306631.stm</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">Berners-Lee, Tim; Connolly, Daniel "Dan" (March 1993). Hypertext Markup Language (draft RFCxxx) (Technical report). p. 28. Archived from the original on 2017-10-23. Retrieved 2017-10-23. <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Berners-Lee, Tim; Masinter, Larry; McCahill, Mark Perry (October 1994). Uniform Resource Locators (URL) (Technical report). (This Internet-Draft was published as a Proposed Standard RFC, RFC 1738 (1994)) Cited in Ang, C. S.; Martin, D. C. (January 1995). Constituent Component Interface++ (Technical report). UCSF Library and Center for Knowledge Management. Archived from the original on 2017-10-23. Retrieved 2017-10-23. <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). Uniform Resource Identifier (URI): Generic Syntax. Network Working Group. doi:10.17487/RFC3986. STD 66. RFC 3986. Internet Standard 66. Obsoletes RFC 2732, 2396 and 1808. Updated by RFC 6874, 7320 and 8820. Updates RFC 1738.
 <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). Uniform Resource Identifier (URI): Generic Syntax. Network Working Group. doi:10.17487/RFC3986. STD 66. RFC 3986. Internet Standard 66. Obsoletes RFC 2732, 2396 and 1808. Updated by RFC 6874, 7320 and 8820. Updates RFC 1738.
 <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). Uniform Resource Identifier (URI): Generic Syntax. Network Working Group. doi:10.17487/RFC3986. STD 66. RFC 3986. Internet Standard 66. Obsoletes RFC 2732, 2396 and 1808. Updated by RFC 6874, 7320 and 8820. Updates RFC 1738.
 <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">The procedures for registering new URI schemes were originally defined in 1999 by RFC 2717, and are now defined by RFC 7595, published in June 2015.[14] <a href="/wiki/RFC_(identifier)" target="_blank">/wiki/RFC_(identifier)</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). Uniform Resource Identifier (URI): Generic Syntax. Network Working Group. doi:10.17487/RFC3986. STD 66. RFC 3986. Internet Standard 66. Obsoletes RFC 2732, 2396 and 1808. Updated by RFC 6874, 7320 and 8820. Updates RFC 1738.
 <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">For URIs relating to resources on the World Wide Web, some web browsers allow .0 portions of dot-decimal notation to be dropped or raw integer IP addresses to be used.[15] <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">T. Berners-Lee; R. Fielding; L. Masinter (August 1998). Uniform Resource Identifiers (URI): Generic Syntax. Network Working Group. doi:10.17487/RFC2396. RFC 2396. Obsolete. Obsoleted by RFC 3986. Updated by RFC 2732. Updates RFC 1808 and 1738.
 <a href="/wiki/Tim_Berners-Lee" target="_blank">/wiki/Tim_Berners-Lee</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Historic RFC 1866 (obsoleted by RFC 2854) encourages CGI authors to support ';' in addition to '&'.[17]: §8.2.1
 <a href="/wiki/RFC_(identifier)" target="_blank">/wiki/RFC_(identifier)</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">W3C (2008). - "An Introduction to Multilingual Web Addresses". 2008-05-09. Archived from the original on 2015-01-05. Retrieved 2015-01-11. <a href="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">http://www.w3.org/International/articles/idn-and-iri/</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">W3C (2014). - Phillip, A. (2014). "What is Happening with "International URLs"". World Wide Web Consortium. Archived from the original on 2015-02-17. Retrieved 2015-01-11. <a href="https://www.w3.org/International/wiki/IRIStatus" target="_blank">https://www.w3.org/International/wiki/IRIStatus</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">IANA (2003). - IANA (2003-02-14). "Completion of IANA Selection of IDNA Prefix". IETF-Announce mailing list. Archived from the original on 2004-12-08. Retrieved 2015-09-03. <a href="https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html" target="_blank">https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">W3C (2008). - "An Introduction to Multilingual Web Addresses". 2008-05-09. Archived from the original on 2015-01-05. Retrieved 2015-01-11. <a href="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">http://www.w3.org/International/articles/idn-and-iri/</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Glaser, J. D. (2014-03-10). Secure Development for Mobile Apps: How to Design and Code Secure Mobile Applications with PHP and JavaScript (1st ed.). CRC Press. p. 193. ISBN 978-1-48220903-7. Retrieved 2015-10-12. <a href="978-1-48220903-7" target="_blank">978-1-48220903-7</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Schafer, Steven M. (2011). HTML, XHTML, and CSS Bible (1st ed.). John Wiley & Sons. p. 124. ISBN 978-1-11808130-3. Retrieved 2015-10-12. <a href="978-1-11808130-3" target="_blank">978-1-11808130-3</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
</ol>

URL open-in-new

URL