This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
URL
URL

Version management

Difference between version and

At line 1 added 84 lines
!!! Overview[1]
[{$pagename}] or A [Uniform Resource Locator] is defined in [RFC 1738] is a reference to a resource that specifies the location of the resource on a computer network and a mechanism for retrieving the resource.A [{$pagename}] is a specific type of uniform resource identifier [URI], although many people use the two terms interchangeably.
A [{$pagename}] implies the means to access an indicated resource, which is not true of every URI.
[{$pagename}]s 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.
!! [{$pagename}] Format
Every HTTP URL consists of the following, in the given order. Several schemes other than HTTP also share this general format, with some variation.
* schema - the scheme name (commonly called protocol, although not every URL scheme is a protocol, e.g. mailto is not a protocol)
* a colon,
* two slashes
* a host, normally given as a domain name
* optionally a colon followed by a port number
* the full path of the resource which can be broken down into:
** path
** query_string
** fragment_id
The scheme says how to connect, the host specifies where to connect, and the remainder specifies what to ask for.
The syntax in more detail is:
[{Image src='/images/url-example.png' caption='URL Format' align ='left' style='font-size: 120%;'}]\\
OR:
{{{
scheme://domain:port/path?query_string#fragment_id
}}}
! Scheme
The scheme, which in many cases is the name of a [protocol] (but not always), defines how the [resource] will be obtained. [Examples] include [http|HTTP], https, [ldap|LDAP], ftp, file and many others. Although schemes are [case-insensitive], the canonical form is lowercase.
! Domain Name
The [domain name|DNS Domain] or literal numeric [IP Address] gives the destination location for the [{$pagename}]. A literal numeric [IPv6] address may be given, but must be enclosed in {{{
[ ] e.g. [db8:0cec::99:123a].
}}}
The domain google.com, or its numeric IP address 173.194.34.5, is the address of Google's website.
The domain name portion of a URL is [case-insensitive] since DNS ignores case:
{{{
http://en.example.org/ and HTTP://EN.EXAMPLE.ORG/ both open the same page.
}}}
! Port
The port number, given in decimal, is optional; if omitted, the default for the scheme is used.
For example,
{{{
http://vnc.example.com:5800
}}} connects to port 5800 of vnc.example.com, which may be appropriate for a VNC remote control session.
If the port number is omitted for the scheme http: URL, the browser will connect on port 80, the default [HTTP] [port]. The default port for a scheme https: request is 443.
! Path
The path is used to specify and perhaps find the [resource] requested. This path may or may not describe folders on the [File System] in the web server. It may be very different from the arrangement of folders on the web server. The path 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.example.org/wiki/URL is correct, then http://en.example.org/WIKI/URL or http://en.example.org/wiki/url will display an HTTP 404 error page, unless these URLs point to valid resources themselves.
! Query String
The query string contains [case-sensitive] data to be passed to software running on the server. It may contain name/value pairs separated by ampersands, for example:
{{{
?first_name=John&last_name=Doe.
}}}
The "?" indicates the start of the Query String and each additional parameter, if present, is separated by "&"
! The fragment identifier
The fragment identifier, if present, specifies a part or a position within the overall resource or document.
When used with HTML, it usually specifies a section or location within the page, and used in combination with Anchor elements or the "id" attribute of an element, the browser is scrolled to display that part of the page.
!! [URIs, URLs, and URNs]
What is the difference between [URIs, URLs, and URNs]?
!! History
[The History of the URL|https://blog.cloudflare.com/the-history-of-the-url/|target='_blank'] is a fun and for some of us a reflection on the past.!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Uniform resource locator|Wikipedia:Uniform_resource_locator|target='_blank'] - based on 2015-02-18
* [#2] - [Guidelines for URL Display|https://chromium.googlesource.com/chromium/src/+/master/docs/security/url_display_guidelines/url_display_guidelines.md|target='_blank'] - based on information obtained 2019-11-04
* [#2] - [The History of the URL|https://blog.cloudflare.com/the-history-of-the-url/|target='_blank'] - based on information obtained 2020-04-17
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop