URL: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
A Uniform Resource Locator (URL) is a string instrucing a client how to request a specific [[resource]]. They always consist of a scheme (like https) and a scheme specific part (like //www.example.com). | A Uniform Resource Locator (URL) is a string instrucing a client how to request a specific [[resource]]. They always consist of a scheme (like https) and a scheme specific part (like //www.example.com). | ||
The format of a URL is standardized in [https://tools.ietf.org/html/rfc1738 rfc1738]. | |||
== Uniform Resource Identifiers == | == Uniform Resource Identifiers == | ||
The term URL and URI are often confused for each other. A Universal Resource Locator has enough information for a client to actually get the resource. This is not always true for a URI. An example of a URI is: | The term URL and URI are often confused for each other. A Universal Resource Locator has enough information for a client to actually get the resource. This is not always true for a URI. An example of a URI is: | ||
urn:isbn:0131103628 | urn:isbn:0131103628 | ||
[[Category: Terminology]] | |||
[[Category: RFCs]] | |||
Latest revision as of 09:22, 3 December 2020
A Uniform Resource Locator (URL) is a string instrucing a client how to request a specific resource. They always consist of a scheme (like https) and a scheme specific part (like //www.example.com).
The format of a URL is standardized in rfc1738.
Uniform Resource Identifiers
The term URL and URI are often confused for each other. A Universal Resource Locator has enough information for a client to actually get the resource. This is not always true for a URI. An example of a URI is:
urn:isbn:0131103628