大网数据广告活动
网站运营与故障问答

Why does Chrome resolve websitename.localhost as localhost?

· 52CE 我爱测

I've been using .localhost as a TLD for locally hosted sites that I am working on. Usually when I start a new site I create an entry in the apache virutal host configuration file and then add an entry in Windows' hosts file to ma…

问题原文

原帖链接 · Cave Johnson · CC BY-SA 3.0

I've been using .localhost as a TLD for locally hosted sites that I am working on. Usually when I start a new site I create an entry in the apache virutal host configuration file and then add an entry in Windows' hosts file to map the address to 127.0.0.1. The address would be something like sitename.localhost

Today I was working on a new site so I added the entry in the virtual hosts file but I forgot to add an entry to the hosts file. To my surprise the site loaded fine in Chrome without mapping the address to 127.0.0.1. However when I tried to load the site in IE and Firefox, it didn't work and my ISP's website showed up instead.

Is there a reason why Chrome does this and other browsers do not? Is this something that is supposed to happen?

已采纳解答

原帖链接 · MrWhite · CC BY-SA 3.0

From the Wikipedia entry for .localhost (TLD):

As a top-level domain, the name has traditionally been defined statically in host DNS implementations with address records (A and AAAA) pointing to the same loopback addresses.

However, as you have found, it would appear that it's just Chrome and later versions of Opera (possibly the WebKit browsers, so might include Safari also) that appear to do this.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2016-01-08)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。