“URL”的意思、由来-开放百科全书

A Uniform Resource Locator (URL), colloquially termed a web address,{{sfnp|W3C|2009}} is a reference to a web resource that specifies its location on a computer network and a mechanism for retrieving it. A URL is a specific type of Uniform Resource Identifier (URI),^[1]{{sfnp|RFC 3986|2005}} although many people use the two terms interchangeably.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}}{{efn|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.{{sfnp|RFC 2396|1998}}{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}} Thus http://www.example.com is a URL, while www.example.com is not.^[2]}} URLs occur most commonly to reference web pages (http), but are also used for file transfer (ftp), email (mailto), database access (JDBC), and many other applications.

Most web browsers display the URL of a web page above the page in an address bar. A typical URL could have the form http://www.example.com/index.html, which indicates a protocol (http), a hostname (www.example.com), and a file name (index.html).

History

Uniform Resource Locators were defined in {{IETF RFC|1738}} in 1994 by Tim Berners-Lee, the inventor of the World Wide Web, and the URI working group of the Internet Engineering Task Force (IETF),{{sfnp|W3C|1994}} as an outcome of collaboration started at the IETF Living Documents Birds of a feather session in 1992.{{sfnp|IETF|1992}}{{sfnp|Berners-Lee|1994}}

The format combines the pre-existing system of domain names (created in 1985) with file path syntax, where slashes are used to separate directory and filenames. Conventions already existed where server names could be prefixed to complete file paths, preceded by a double slash (//).{{sfnp|Berners-Lee|2000}}

Berners-Lee later expressed regret at the use of dots to separate the parts of the domain name within URIs, wishing he had used slashes throughout,{{sfnp|Berners-Lee|2000}} and also said that, given the colon following the first component of a URI, the two slashes before the domain name were unnecessary.{{sfnp|BBC News|2009}}

An early (1993) draft of the HTML Specification^[3] referred to "Universal" Resource Locators. This was dropped some time between June 1994 (RFC 1630) and October 1994 (draft-ietf-uri-url-08.txt).^[4]

Syntax

Every HTTP URL conforms to the syntax of a generic URI. {{#section:Uniform resource identifier|syntax}}

A web browser will usually dereference a URL by performing an HTTP 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 secure connection to the website.

Internationalized URL

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 Internationalized Resource Identifier (IRI) is a form of URL that includes Unicode characters. All modern browsers support IRIs. The parts of the URL requiring special treatment for different alphabets are the domain name and path.{{sfnp|W3C|2008}}{{sfnp|W3C|2014}}

The domain name in the IRI is known as an Internationalized Domain Name (IDN). Web and Internet software automatically convert the domain name into punycode usable by the Domain Name System; for example, the Chinese URL http://例子.卷筒纸 becomes http://xn--fsqu00a.xn--3lr804guic/. The xn-- indicates that the character was not originally ASCII.{{sfnp|IANA|2003}}

The URL path name can also be specified by the user in the local writing system. If not already encoded, it is converted to UTF-8, and any characters not part of the basic URL character set are escaped as hexadecimal using percent-encoding; 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.{{sfnp|W3C|2008}}

Protocol-relative URLs {{anchor|prurl}}

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, either HTTP or HTTPS.^[5]^[6]

See also

Notes

Citations

1. ^{{Cite web|url=https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/|title=Forward and Backslashes in URLs|website=zzz.buzz|language=en|access-date=2018-09-19}}
2. ^{{Cite web|url=https://danielmiessler.com/study/url-uri/#gs.Hs64zOs|title=The Difference Between URLs and URIs|last=Miessler|first=Daniel|date=|website=|archive-url=|archive-date=|dead-url=|access-date=}}
3. ^{{cite techreport |title=Hypertext Markup Language (draft RFCxxx) |first1=Tim |last1=Berners-Lee |first2=Daniel |last2=Connolly |date=March 1993 |page=28 |url=https://www.ucc.ie/archive/curia/dtds/html-spec.ps}}
4. ^{{cite techreport |title=Uniform Resource Locators (URL) |first1=T |last1=Berners-Lee |first2=L |last2=Masinter |first3=M |last3=McCahill |date=October 1994 |url=http://ds.internic.net/internet-drafts/draft-ietf-uri-url-08.txt}} cited in {{cite techreport |title=Constituent Component Interface++ |first1=C.S. |last1=Ang |first2=D.C. |last2=Martin | publisher=UCSF Library and Center for Knowledge Management |date=January 1995 |url=https://listserv.heanet.ie/cgi-bin/wa?A2=ind9501&L=HTML-WG&P=R23201&X=C6F9505B05BC9A3B67&}}
5. ^{{cite book |url=https://books.google.com/books?id=6u2sBAAAQBAJ&pg=PA193 |title=Secure Development for Mobile Apps: How to Design and Code Secure Mobile Applications with PHP and JavaScript |publisher=CRC Press |author= J. D. Glaser |year=2013 |page=193 |accessdate=12 October 2015}}
6. ^{{cite book |url=https://books.google.com/books?id=DW0uyBZzEDwC&pg=PT124 |title=HTML, XHTML, and CSS Bible |publisher=John Wiley & Sons |author=Steven M. Schafer |year=2011 |page=124 |accessdate=12 October 2015}}