SoylentNews is people
SoylentNews
Google Achieves Its Goal of Erasing the WWW Subdomain From Chrome
With the release of Chrome 79, Google completes its goal of erasing www from the browser by no longer allowing Chrome users to automatically show the www trivial subdomain in the address bar.
When Chrome 76 was released, Google decided to no longer show the www "trivial subdomain" in the address bar when visiting a web site. This means, that if you are visiting www.bleepingcomputer.com, Chrome would only show bleepingcomputer.com in the address bar...
[...] According to a Google engineer, www is considered a trivial subdomain because "this isn't information that most users need to concern themselves with in most cases".
Many users, though, felt that this was a security issue, could be confusing for users, and is technically incorrect because www.domain.com is not always the same host as domain.com.
So is this a distinction without a difference or a real issue?
(Score: 0) by Anonymous Coward on Monday December 16 2019, @12:05AM
Yeah, GP should try it himself and look at the PTRs and ASNs. That will make crystal clear you are getting the random machines from the pool. The reason why www.pool.ntp.org is consistent is because it is the deprecated URL for the NTP pool project, and therefore controlled by the NTP project through their CDN. There is no guarantee that the page you get from pool.ntp.org matches www.pool.ntp.org because it isn't under the pool project's control. In fact, most servers you contact at pool.ntp.org won't run web servers at all, or redirect you out of courtesy (which is why you did, because the browser probably tried a couple of the addresses returned until one responded with a redirect). But that isn't a hard requirement nor can the NTP pool guarantee it.