Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

Post reply on HN
Print view View original

341–350 of 919 posts

Re: Chrome 69: “www.” subdomain missing from URL

#341

Post by king_phil »

vinceguidry wrote: post #266
jbob2000 wrote: post #261

Earlier quoted context omitted.

You didn't read far enough: > "subdomain.www.domain.com" displays as "subdomain.domain.com". This is very deceiving. This change gives phishers a huge opportunity.

I agree with the spirit of the change, not necessarily every detail of the implementation.

The implementation will definitely need a up to date Public Suffix List. We control a bunch of public suffixes and it's a huge, huge difference if you browse to the address "www.com" or to "com" - or blogger.com and www.blogger.com, or dyndns.org vs. www.dyndns.org. In this case, there are different organizations/persons controlling these.

Should you not know which one you have connected to?

Re: Chrome 69: “www.” subdomain missing from URL

#342

Post by manigandham »

meowface wrote: post #205
Klonoar wrote: post #74

Earlier quoted context omitted.

Same exact reason that api.domain.com or beta.domain.com matters - you're on a subdomain, not the root domain. That the internet and world at large made www the "kind of" root domain in many cases is an unfortunate thing, but I've not seen a modern server configuration that doesn't handle this case by default.

But when using HTTP(S), you nearly always expect the "www." domain and the root domain to host the same content. It's very, very rare that this isn't the case. Chrome appears to be hiding "m.", too, which is unfortunate (as would api. or beta. being hidden), but "www." is such boilerplate for HTTP at this point that I don't think it matters whether it's displayed or not.

If it doesnt matter, why even remove it?

Re: Chrome 69: “www.” subdomain missing from URL

#343

Post by king_phil »

lozenge wrote: post #79
teilo wrote: post #36

Earlier quoted context omitted.

That's not the case. I run a server that does not respond to "www." If I enter "www.myserver.com" into the address bar, I get a DNS lookup failure, but the address bar is now showing "myserver.com." That's damn confusing, and this is an idiotic default on Chrome's part.

That seems like an edge case worth submitting a separate bug for.

Think public suffixes! It is long, so definitely not an edge case.

You can write a small script to look up all PSL domains and check if the www and APEX domain has the same dns records.

Our implementation (we control 15 or so) does not, have a www-subdomain for the domains. Anybody can register the www-subdomains.

Re: Chrome 69: “www.” subdomain missing from URL

#344

Post by lmedinas »

wolco wrote: post #311

I hope people start moving from chrome to firefox. The standards they pushing are harming the web in ways.

i use Firefox @ work and @home for serious stuff. The only reason i don't use Firefox 100% is due to the Android app which is a lag fest.

Mozilla needs to put more resources on Android.

Re: Chrome 69: “www.” subdomain missing from URL

#345

Post by ChristianBundy »

fastball wrote: post #328
wolco wrote: post #311

I hope people start moving from chrome to firefox. The standards they pushing are harming the web in ways.

If only Firefox's JS handling didn't melt my laptop.

Yeah, I switched from Firefox to Epiphany (also called GNOME Web[0]) and I have the best of both worlds: a WebKit browser that's more feature-complete than luakit/surf/etc., with Firefox sync integration and no Google.

It's like an open source Safari clone and it works beautifully.

[0]: https://wiki.gnome.org/Apps/Web

Re: Chrome 69: “www.” subdomain missing from URL

#346

Post by Domenic_S »

howard941 wrote: post #332
brockers wrote: post #269

Earlier quoted context omitted.

No this is simply bad implementation. As has already been mention, for internet services that also have websites for those services the www. subdomain makes total sense. > How will you distinguish http://www.pool.ntp.org vs http://pool.ntp.org ? In the above case pool.ntp.org is a decades old time service, while www.pool.ntp.org is a website describing the service.

Do you get something at http://pool.ntp.org ? My blowser times out as does telnetting to port 80

ntp is UDP so telnet isn't going to work. Try this:

$ ntpdate -d pool.ntp.org

Re: Chrome 69: “www.” subdomain missing from URL

#349

Post by mindcrime »

rocky1138 wrote: post #179
pishpash wrote: post #85

Earlier quoted context omitted.

Until a few releases down the line and it is decided for you that the flag should be removed.

This is the problem. Better to just switch to Firefox now and be done with it. Hopefully it'll send a message.

Until Firefox leadership decide to make the same change "because that's what Chrome does". Sadly, over the history of Firefox (and before that, Mozilla/Seamonkey) the leadership there has always been WAY too obsessed with following IE and/or Chrome rather than just building the best browser and taking some chances.

Seriously, trawl through Bugzilla sometime and look how many bugs are closed with the the justification being some variation of "That's how IE does it" or "IE doesn't support that", etc. And then substitute "Chrome" for "IE" later in history once Chrome took over the universe.

Post reply on HN