JavaScript’s Location object provides access to components of the current URL. One can think of this object as a read-only window at the current location.
The Location object has two properties that are often confused with: host and hostname.
The host property returns the host name, port number, and protocol of the current URL. For example, if the current URL is "http://example.com:8080/path/to/page.html", the value of host is "example.com:8080".
Using location.host also has some advantages over location.hostname.
First, it's more specific. If you need a port number or protocol, you can be sure the host properties will return it.
Second, more concise. If you only need the hostname, you can use the shorter hostname attribute. But if you also need the port number or protocol, you can use the host properties and get all the information at once.
Third, it is more future-oriented. If a new URL component is added, it may be included in the host property. This is not necessarily the case with the hostname attribute.
On the other hand, the hostname attribute returns only the hostname portion of the current URL. For example, if the current URL is "http://example.com:8080/path/to/page.html", the value of hostname is "example.com".
Using location.hostname has some advantages over location.host.
First, it's more readable. When you look at a URL, you're usually more interested in the hostname than the port number or protocol.
Second, more consistent. The hostname is a required part of the URL, while the port number and protocol are optional. This means that not all URLs have a host attribute, but they all have a hostname.
Third, it is more flexible. If you change the port number or protocol of the URL, the hostname will still be the same. This is not the case with host properties.
In general, unless you specifically need a port number or protocol, you should use location.hostname.
The reason is that the hostname is the "human-readable" part of the URL, while the host attribute also includes the port number and protocol. Most of the time, this additional information is not needed.
However, there are some exceptions. An example is if you need to construct a new URL using the current URL as a base. In this case, you need to use location.host to preserve the port number and protocol.
Another exception is if you use a URL shortener. In this case, you need to use location.host to preserve the hostname of the original URL.
The following table highlights the main differences between location.host and location.hostname in JavaScript -
| Comparatively basic | Location.Host | Location.Hostname |
|---|---|---|
| definition | The host attribute returns the host name, port number and protocol of the current URL | On the other hand, the hostname attribute returns only the hostname portion of the current URL |
| Example | If the current URL is "http://example.com:8080/path/to /page.html", the value of the host is "example.com:8080 | If the current URL is "http://example.com:8080/path /to/page.html", the value of the host name is "example.com". |
| When to use? | If you specifically need a port number or protocol, you should use location.host. | Unless you specifically need a port number or protocol, you should use location.hostname. |
| readability | The host properties also include the port number and protocol, making it less readable. | The hostname is the "human-readable" part of the URL. |
In most cases, you should use location.hostname instead of location.host. It's more readable, more consistent, and more resilient. However, there are some exceptions, such as when you need to construct a new URL or use a URL shortener.
The above is the detailed content of Difference between location.host and location.hostname in JavaScript. For more information, please follow other related articles on the PHP Chinese website!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
