Live data from Hacker News

Chrome 69: “www.” subdomain missing from URL

bugs.chromium.org

761–770 of 919 posts

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

#761

Earlier quoted context omitted.

> Arguably, the most sincere problems arise from mixed alphabets with Unicode domains and look-alike characters/glyphs. No way. The most sincere problem is that hostnames do not enforce any binding to a real world identity that users can understand (nobody inspects certs) and that the most trustworthy component of a hostname is the second to the last section (right before ".com"). Humans tend to look at the front of…

The best security change we could make, imo, is rewriting domains so that they look like com.evil.bank.www/now/urls/go/from/most/specific/to/least

Years ago, before the WWW, some parts of the world indeed ordered them that way.

* https://en.wikipedia.org/wiki/JANET_NRS

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

#762
post #739

Earlier quoted context omitted.

Wow, that's particularly deranged if "service.at/search?q=acme" is considered acceptable (and if that 's not, how could any search work?). Thanks for the explanation. I honestly would not have imagined anything like that.

IANAL, and I'm just speculating here, but the law could have been termed as "copyright laws apply to domain names on the internet" (i.e you can't use the name of a brand you don't own in a domain name), and acme.service.at is a domain name, but service.at/search?q=acme is not.

That would be trademark, not copyright, by the way.

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

#763
post #746

Earlier quoted context omitted.

I don't remember the site offhand, but I was going to one recently where example.com didn't even work, it was some weird error page -- you had to use www.example.com. If it comes to me, I'll post it.

This is what Chrome's update is trying to fix. Developers are confuser when setting up dns if they should have www or not have www or only have www...

Not really fixing it thou because they just strip the www part from the name. If the developer does not setup www.domain.com and the user goes there chrome will not “fix” anything.

I haven’t tested it but it will most likely show up as domain.com in the address bar and will result in an error show to the customer.

If chrome wants to strip www as it’s essentially the same domain.com they can submit an RFC and not just decide for everyone. Honestly I hope they start making more stupid decisions like this so ppl move to Firefox so we have more competition.

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

#764

Earlier quoted context omitted.

I just downloaded canary and tried it and you are absolutely right. about.www.github.io shows as about.github.io I'm on board with this change in general, but this is absolutely something that needs to be fixed. Not only is that just annoying and wrong, but it could be dangerous in some situations. Also, it doesn't just stop at one removal. http://www.www.about.www.www.stuff.www.www.example.com shows as about.stuff.e…

I'm guessing this is implemented as s/www\.//

Here is the implementation: https://github.com/chromium/chromium/blob/master/components/...

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

#765

Earlier quoted context omitted.

What if the user sees "Wik1pedia.org/wiki/Canada"? Or "аррӏе.com"? Hiding random parts of the address isn't going to make browsing the web better. The main purpose of URLs is for hyperlinks, not as a highly intuitive user interface. Users who don't know how URLs work don't care what is up there. They only care that what they are looking at is what they expect, and a way to get to where they want to go. And that's a c…

Users don't see that. Expecting users to use the URL bar to detect phishing via homoglyphs is insanity.

Right. So messing with the URL bar is pointless. If people actually don't like it, get rid of it, but provide some other means to establish authenticity of what you're looking at.

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

#766

Earlier quoted context omitted.

You should really give the Brave browser from (www.)brave.com a try.

Yes. I've been using Brave exclusively for more than a year and I'm not going back. I'm still undecided on which search engine to use though.

Have you tried Searx? Meta search engine, open source, multiple instances (domains) to choose from. Once configured to your particular needs, searx can prove very powerful.

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

#767
>Why is www hidden twice if the domain is "www.www.2ld.tld"?

plus

>"subdomain.www.domain.com" displays as "subdomain.domain.com".

and

>http://m.tumblr.com/ [1]

Hoo boy. Can we officially call this a "shit-storm"? It seems extremely poorly thought through.[2]

[1] seriously, visit that right now. utterly brilliant username, I wish them all the best.

[2] unless you want to sell invisible AMP URLs. but then I want you to lose your job.

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

#768

Earlier quoted context omitted.

m. is where you often receive a feature degraded, app-walled, or sign-in walled website that isn't present on the full-featured website. I want to know that I'm receiving a degraded version of a website and that maybe dropping the m. will restore it.

It's also where you receive a lightweight, fast, to the point version. Admittedly, it's not just "m", but If I _must_ use Facebook the only bearable version is mbasic.facebook.com

It’s certainly not true in the case of Reddit. Their mobile site is horrible by any measure, way slower than the old desktop site.

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

#769

Considering a subdomain "trivial" is ridiculous... there's a difference between "www.example.com" and "example.com". Not only can they serve different sites, they can even have different DNS records! It seems that "m." is also considered a trivial subdomain. So when a user clicks a link to a "m.facebook.com" uri, they'll be confused why FB looks different when the browser reports it's on "facebook.com". I sincerely h…

Oh come on. "www." was used as a way of delineating what was a web address. Hence the fashion of putting that there so people knew you had to do it in the browser. Before then people used to also put the " http://" on there, and the combination of the two on vehicles/signs was ridiculous. We're now in a web world. People know what a URL is. "domain.com" isn't ambiguous, it's obvious to man, beast or child that you ty…

This whole comment is two-faced.

People know what a URL is. But this issue demonstrates misunderstandings of URLs, as "www.x.y" is not necessarily an official "x.y" page.

"www" == "web address", or "m. is ridiculous" which are annoying fashions (agreed there!), but that has literally zero impact on the security characteristics, implying yet again that people do not understand URLs.

---

No. This comment is a perfect example of why this is not safe to do. It's throwing open the door to abuse.

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

#770
The point of this change is not to mess with www. or m. any other subdomain. The real reason for this change is obviously from latest google moves is to hide one and only one subdomain from users - amp. They really don't want you to know when you are not on independent website but actually inside google silo, playing by google rules.
Post reply on HN