There are (at least) three ways to link to a resource:
href="foo/bar.html"
href="/foo/bar.html"
href="http://example.com/foo/bar.html"
The first is a "relative url", no problem. But I've seen (2) and (3) both referred to as an "absolute url". Which is correctly termed an "absolute url", and what is the proper name of the other?
(Bonus points for references to relevant standards or other official documentation.)
An absolute URL contains all the information necessary to locate a resource. A relative URL locates a resource using an absolute URL as a starting point. In effect, the "complete URL" of the target is specified by concatenating the absolute and relative URLs.
A fully-qualified domain name (FQDN) is that portion of an Internet Uniform Resource Locator (URL) that fully identifies the server program that an Internet request is addressed to.
If you prefix the URL with // it will be treated as an absolute one. For example: <a href="//google.com">Google</a> . Keep in mind this will use the same protocol the page is being served with (e.g. if your page's URL is https://path/to/page the resulting URL will be https://google.com ).
Linking with absolute URLs The domain is the name of the website. For example, the domain name of Indiana University's central web server is www.indiana.edu . The path includes directory and file information. You must use absolute URLs when referring to links on different servers.
RFC 3986 defines Uniform Resource Identifiers.
A relative reference that begins with a single slash character is
termed an absolute-path reference. A relative reference that does
not begin with a slash character is termed a relative-path reference.
href="foo/bar.html"
is a relative reference, specifically a relative-path reference.href="/foo/bar.html"
is a relative reference with an absolute path
href="http://example.com/foo/bar.html"
is an absolute URI
href="//example.com/foo/bar.html"
is a network-path reference
A relative reference that begins with two slash characters is termed a network-path reference; such references are rarely used.
"Absolute URLs contain a great deal of information which may already be known from the context of the base document's retrieval, including the scheme, network location, and parts of the URL path."
https://www.rfc-editor.org/rfc/rfc1808
The number (2) is an absolute path, the (3) is an absolute URL.
I like the W3's description found here:
A URL is an absolute URL if resolving it results in the same output regardless of what it is resolved relative to, and that output is not a failure.
It doesn't bring up scheme, path, or any other concepts like that, but basically just says that the same input always brings the same output. You can only say that about #3.
I wouldn't get too caught up in the technicalities though - #2 is still absolute if your universe is the website. Also something like //example.com/foo/bar.html
is absolute if your universe is the scheme. I think the word "absolute" in those cases is still meaningful from a developer's perspective.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With