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: 3, Informative) by rigrig on Sunday December 15 2019, @07:10PM (8 children)
Those random people volunteer to run a timeserver and have it added to the NTP pool, you can sign up here [ntppool.org].
They don't get to run www.pool.ntp.org:
www.pool.ntp.org resolves to the NTP pool project webserver (which redirects you to www.ntppool.org).
pool.ntp.org resolves to a random timeserver in the pool, which may or may not be running a webserver as well, which may or may not bother checking the requested hostname.
No one remembers the singer.
(Score: 4, Informative) by EvilSS on Sunday December 15 2019, @08:22PM (4 children)
(Score: 0) by Anonymous Coward on Sunday December 15 2019, @10:50PM (1 child)
I think you are missing the point. You cannot tell, at a glance, if you are looking at a web page provided by the official NTP pool project or a web page provided by a random person with a multi-use server. In addition, how many random people would even realize that clicking and then scrolling the url in the bar to the left would show something different?
(Score: 2) by EvilSS on Monday December 16 2019, @02:56PM
(Score: 2) by Magic Oddball on Sunday December 15 2019, @11:30PM (1 child)
When I checked, the two addresses would load identical webpages, but www.pool.ntp.org has a consistent DNS address of 151.101.190.217 while pool.ntp.org really is returning completely different DNS addresses each time it's accessed.
(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.
(Score: 1, Troll) by FatPhil on Monday December 16 2019, @01:12AM (2 children)
If something attempts to break how the web works, then it becoming broken itself is entirely expected.
Doctor, it hurts when I do >this<.
Well, don't do that then.
Then again, there appears to be some contradiction between your posts, if www. redirects to something sensibly named, nothing confusing happens to either the browser or the server.
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 1, Interesting) by Anonymous Coward on Monday December 16 2019, @03:05AM (1 child)
Unless you type in a domain name without the "www" part of the name because you don't see it in the address bar.
Regardless, I'd be fascinated to know how you think www and sans www not pointing to the same server or duplicating content violates the RFCs.
(Score: 2) by FatPhil on Tuesday December 17 2019, @10:36AM
Yes, not displaying it in the address bar is, to use my own words in this very thread "retarded". Do you have reading comprehension issues?
> Regardless, I'd be fascinated to know how you think www and sans www not pointing to the same server or duplicating content violates the RFCs.
In a twisted way, so would I, as that's not something I think at all, and certainly haven't expressed in this thread. Do you have reading comprehension issues?
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves