Eisspeedway

URL: Difference between revisions

Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Yankeu 14 (talk | contribs)
2 edits
No edit summary
Tag: references removed
Johnuniq (talk | contribs)
Autopatrolled, Administrators
87,101 edits
m Reverted edits by Yankeu 14 (talk) to last version by SmackBot
Line 1: Line 1:
{{Expand|date=March 2008}}
{ NOM : ngueha yankeu }
{{Redirect|URL}}
{{PRENOM : irisse vanessa}}
[[File:URI_Venn_Diagram.svg|thumb|The relationship of URL to [[URI]] and [[Uniform Resource Name|URN]]]]
[[PROFESSION :football]]]
In [[Information technology|computing]], a '''Uniform Resource Locator''' ('''URL''') is a subset of the [[Uniform Resource Identifier]] (URI) that specifies where an identified resource is available and the mechanism for retrieving it. In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a [[synonym]] for URI.<ref>RFC 3305 "URI Partitioning: There is some confusion in the web community over the partitioning of URI space, specifically, the relationship among the concepts of URL, URN, and URI. The confusion owes to the incompatibility between two different views of URI partitioning, which we call the 'classical'
[[CLUB : chanthaburi fc]],
and 'contemporary' views."</ref> In popular language, a URI is also referred to as a ''Web address''{{Citation needed|date=November 2009}}.
[[DATE DE NAISSANCE :14 OCTOBBRE 1988]] (

NATIONALITEE : cameroun
==History==
==History==
The Uniform Resource Locator was created in 1994<ref>http://www.ietf.org/rfc/rfc1738.txt</ref> by [[Tim Berners-Lee]] as part of the URI.<ref name="URL Spec">[http://www.w3.org/Addressing/URL/url-spec.txt URL Specification]</ref> The Uniform Resource Locator evolved out of the ''Universal'' Resource Locator <ref name="SearchNetworking.com Definitions">[http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci213251,00.html SearchNetworking.com Definitions]</ref>. Berners-Lee regrets the use of dots to separate the route to the [[Server_(computing)|server]] in the URI, and wishes he had used slashes for the whole thing{{Citation needed|date=September 2009}}. For example, <tt><nowiki>http://www.serverroute.com/path/to/file.html</nowiki></tt> would look like <tt><nowiki>http:com/serverroute/www/path/to/file.html</nowiki></tt>.
The Uniform Resource Locator was created in 1994<ref>http://www.ietf.org/rfc/rfc1738.txt</ref> by [[Tim Berners-Lee]] as part of the URI.<ref name="URL Spec">[http://www.w3.org/Addressing/URL/url-spec.txt URL Specification]</ref> The Uniform Resource Locator evolved out of the ''Universal'' Resource Locator <ref name="SearchNetworking.com Definitions">[http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci213251,00.html SearchNetworking.com Definitions]</ref>. Berners-Lee regrets the use of dots to separate the route to the [[Server_(computing)|server]] in the URI, and wishes he had used slashes for the whole thing{{Citation needed|date=September 2009}}. For example, <tt><nowiki>http://www.serverroute.com/path/to/file.html</nowiki></tt> would look like <tt><nowiki>http:com/serverroute/www/path/to/file.html</nowiki></tt>.

Revision as of 06:39, 7 November 2009

"URL" redirects here. For other uses, see URL (disambiguation).
The relationship of URL to URI and URN

In computing, a Uniform Resource Locator (URL) is a subset of the Uniform Resource Identifier (URI) that specifies where an identified resource is available and the mechanism for retrieving it. In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a synonym for URI.[1] In popular language, a URI is also referred to as a Web address[citation needed].

History

The Uniform Resource Locator was created in 1994[2] by Tim Berners-Lee as part of the URI.[3] The Uniform Resource Locator evolved out of the Universal Resource Locator [4]. Berners-Lee regrets the use of dots to separate the route to the server in the URI, and wishes he had used slashes for the whole thing[citation needed]. For example, http://www.serverroute.com/path/to/file.html would look like http:com/serverroute/www/path/to/file.html.

Berners-Lee has also "apologised" for the two slashes that precede the server name [1].

Syntax

Main article: URI scheme § Generic syntax

Every URL is made up of some of the following: the scheme name (commonly called protocol), followed by a colon, then, depending on scheme, a hostname (alternatively, IP address), a port number, the pathname of the file to be fetched or the program to be run, then (for programs such as CGI scripts) a query string[5][6], and with HTML files, an anchor (optional) for where the page should start to be displayed.[7]

The combined syntax looks like:
resource_type://username:password@domain:port/filepathname?query_string#anchor

  • The scheme name, or resource type, defines its namespace, purpose, and the syntax of the remaining part of the URL. Most Web-enabled programs will try to dereference a URL according to the semantics of its scheme and a context. For example, a Web browser will usually dereference the URL http://example.org:80 by performing an HTTP request to the host example.org, at the port number 80. Dereferencing the URN mailto:bob@example.com will usually start an e-mail composer with the address bob@example.com in the To field.
    • Other examples of scheme names include https: gopher:, wais:, ftp:. URLs that specify https as a scheme (such as https://example.com/) denote a secure website.
  • The registered domain name or IP address gives the destination location for the URL. The domain google.com, or its IP address 72.14.207.99, is the address of Google's website.
  • The hostname and domain name portion of a URL are case-insensitive since the DNS is specified to ignore case. http://en.wikipedia.org/ and HTTP://EN.WIKIPEDIA.ORG/ both open the same page.
  • The port number is optional; if omitted, the default for the scheme is used. For example, if http://myvncserver.no-ip.org:5800 is typed into the address bar of a browser it will connect to port 5800 of myvncserver.no-ip.org; this port is used by the VNC remote control program and would set up a remote control session. If the port number is omitted a browser will connect to port 80, the default HTTP port.
  • The file path name is used to find the information or program specified. It is case-sensitive, though it may be treated as case-insensitive by some servers, especially those based on Microsoft Windows. If the server is case sensitive and http://en.wikipedia.org/wiki/URL is correct, http://en.wikipedia.org/WIKI/URL/ or http://en.wikipedia.org/wiki/url/ will display an HTTP 404 error page.
  • The query string contains data to be passed to web applications such as CGI programs. The query string contains name/value pairs separated by ampersands, with names and values in each pair being separated by equal signs, for example first_name=John&last_name=Doe.
  • The anchor part when used with HTTP specifies a location on the page. For example http://en.wikipedia.org/wiki/URL#Syntax addresses the beginning of the Syntax section of the page.

Absolute vs relative URLs

An absolute URL is one that points to the exact location of a file. It is unique, meaning that if two absolute URLs are identical, they point to the same file.[8] An example is: http://en.wikipedia.org/wiki/File:Raster_to_Vector_Mechanical_Example.jpg

A relative URL points to the location of a file from a point of reference. This reference is usually the directory beneath the file.[8] It is preceded by two dots (../directory_path/file.txt) for the directory above, one dot (./directory_path/file.txt) for the current directory or without the beginning slash (directory_path/file.txt), which is also the current directory.

URLs as locators

In its current strict technical meaning, a URL is a URI that, “in addition to identifying a resource, provides a means of locating the resource by describing its primary access mechanism (e.g., its network ‘location’).”[9][10]

Internet hostnames

Main article: Hostname

On the Internet, a hostname is a domain name assigned to a host computer. This is usually a combination of the host's local name with its parent domain's name. For example, "en.wikipedia.org" consists of a local hostname ("en") and the domain name "wikipedia.org". This kind of hostname is translated into an IP address via the local hosts file, or the Domain Name System (DNS) resolver. It is possible for a single host computer to have several hostnames; but generally the operating system of the host prefers to have one hostname that the host uses for itself.

Any domain name can also be a hostname, as long as the restrictions mentioned below are followed. So, for example, both "en.wikimedia.org" and "wikimedia.org" are hostnames because they both have IP addresses assigned to them. The domain name "pmtpa.wikimedia.org" is not a hostname since it does not have an IP address, but "rr.pmtpa.wikimedia.org" is a hostname. All hostnames are domain names, but not all domain names are hostnames.

See also

References

  1. ^ RFC 3305 "URI Partitioning: There is some confusion in the web community over the partitioning of URI space, specifically, the relationship among the concepts of URL, URN, and URI. The confusion owes to the incompatibility between two different views of URI partitioning, which we call the 'classical' and 'contemporary' views."
  2. ^ http://www.ietf.org/rfc/rfc1738.txt
  3. ^ URL Specification
  4. ^ SearchNetworking.com Definitions
  5. ^ RFC 1738
  6. ^ PHP parse_url() Function, retrieved 2009-03-12
  7. ^ URL Syntax
  8. ^ a b Absolute vs Relative URLs
  9. ^ Tim Berners-Lee, Roy T. Fielding, Larry Masinter. (January 2005). “Uniform Resource Identifier (URI): Generic Syntax”. Internet Society. RFC 3986; STD 66.
  10. ^ by describing its primary access mechanism
  • RFC 3986 Uniform Resource Identifier (URI): Generic Syntax [Text] [HTML]
Quelle: https://en.wikipedia.org/wiki/Special%3ADiff%2F324418675