According to spec and semantics is protocol and host combined: https://example.com
still called a host, or is this called a URL, URI, or something else?
Also, is (https) called protocol or scheme? NGINX uses scheme, but I don't see any reference to that origin.
The Host Identity Protocol (HIP) is a host identification technology for use on Internet Protocol (IP) networks, such as the Internet. The Internet has two main name spaces, IP addresses and the Domain Name System. HIP separates the end-point identifier and locator roles of IP addresses.
A URL (Uniform Resource Locator) is a unique identifier used to locate a resource on the Internet. It is also referred to as a web address. URLs consist of multiple parts -- including a protocol and domain name -- that tell a web browser how and where to retrieve a resource.
The second part is sometimes “www.” WWW stands for “World-Wide Web.” Including a www. before the url used to be standard, but it is unnecessary in the modern web. The third part is the domain name, like google.com, or whitehouse.gov.
protocol, in computer science, a set of rules or procedures for transmitting data between electronic devices, such as computers. In order for computers to exchange information, there must be a preexisting agreement as to how the information will be structured and how each side will send and receive it.
I think the term you may really be looking for is origin, as in RFC 6454.
An origin isn’t just scheme+host, but scheme+host+port, and URLs like https://example.com
aren’t actually just scheme+host — because they express a (default) port too: 443, the default TLS port — just as in http://example.com
there’s a built-in expression that the port is 80.
I’m not sure what the context was for the original question here, but I know a common case that would normally motivate somebody to want to know what a combination of scheme+host is called is the case where you want to compare two URLs that either have the same host but different schemes, like https://example.com
and http://example.com
, or that have the same scheme and host but different ports, like http://example.com
and http://example.com:8888
. And consideration of comparing URLs that way will eventually take you to thinking of them in terms of the "same origin" policy that the entire Web security model is based on.
IMHO, origin is not the correct term, since origin refers to "where the communication comes from". But it can also be a destination. Therefore, I think Base URL is the best-fitting term for protocol+host+port. See e.g. https://www.techopedia.com/definition/4858/base-url .
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