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

791–800 of 919 posts

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

#791

Post by vinceguidry »

king_phil wrote: post #341
vinceguidry wrote: post #266

Earlier quoted context omitted.

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?

I think an exception list rather than a straight map is all that's needed. If you want to buck the convention, fine, don't expect the browsers to know what you're trying to do, so update this list, which takes 30 days to propagate, and you can have your fun.

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

#792

Post by EmpirePhoenix »

mirko22 wrote: post #712
Godel_unicode wrote: post #693

Earlier quoted context omitted.

I think the spark plugs example is an excellent one. People used to require an extensive knowledge of how cars worked in order to have a prayer of using them effectively. Now they don't, because we realized none of that knowledge is necessary if you design the system correctly. We have enough historical context to realize that things like parsing URLs by eye is unsafe for the general population, and always will be. T…

when did you have to know how spark plugs work to drive a car? And isn’t this why car mechanics exist? On the other hand you had to learn at some point what and RPM gauge is... And we still have it in cars even though you could say you don’t really need it.

My car does not have a RPM gauge, instead it has two arrows that suggest when to gear up or down (it is manual)

One could say the interface was dumbed down to the minimum.

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

#793

Post by dTal »

sofaofthedamned wrote: post #497
parliament32 wrote: post #118

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…

I disagree about the 'm.domain' convention; it's good and useful. I like the ability to retrieve a mobile site on my desktop, and vice versa. Sometimes I'll be on a site that's difficult to read on mobile, and speculatively try the 'm.domain' - often it will work. When the site itself tries to autodetect what device I'm using, it often makes a poor decision that is not subject to appeal.

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

#794

Post by [deleted] »

lvs wrote: post #238
crispyporkbites wrote: post #172

Earlier quoted context omitted.

It's not a shoddy implementation on Citibank's part. Google are just fucking the web over so we all have to fit their structure. This is standard incumbent behaviour, they are drawing up the moat bridge, inch by inch.

I think the downvotes here are uncalled-for. This is correct. Google is leveraging a dominant market position to make seemingly frivolous changes that will ultimately benefit them commercially. Come on, you know where this is going: They are going to hide amp subdomain, so you don't know if you're looking at AMP or the actual destination. And then suddenly the whole world funnels through AMP.

[deleted]

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

#796

Post by foozed »

PostOnce wrote: post #779
foozed wrote: post #776

Earlier quoted context omitted.

I use Firefox as my "at home" / private browser. However for work i unfortunately feel forced to continue using chrome. First I just really prefer the chrome devtools and i just can't seem top find an equivalent replacement for the "manage people"/multi user built ion function that chrome offers. I really wish Firefox had something similar...

firefox has both profiles (for actual different users) and containers for isolating stuff (i.e. a sub-profile) for a single user. The containers have a great UI/UX. I'm looking at the profile stuff now (after having not in years) and it seems counterintuitive and clunky https://support.mozilla.org/en-US/kb/profile-manager-create-... https://support.mozilla.org/en-US/kb/containers Anyway, "forced" is a strong word whe…

the containers are great thanks for sharing, will definitely use those at home! You're right I should have emphasized the feel part of my comment since the dev tools especially are just a matter of preference. However I stand by my point that the profiles are definitely not on par with chrome, since there doesn't seem to be a way to have multiple profiles open at once.

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

#797

Post by JdeBP »

EvanAnderson wrote: post #533
tatersolid wrote: post #449

Earlier quoted context omitted.

You lack the compassion that comes with experience. My $dayjob has our AD root domain the same as our public root domain. Because we implemented AD in the year 2000, and this was Microsoft’s recommendation for domain naming way back then. And if you use Exchange, you can’t rename your AD domain, you have to rebuild your forest and migrate piecemeal. So we’re stuck with it. The practice of using Corp.example.com did n…

This one is kind of a "religious" topic for me, I guess. I'm sorry that it is, but it makes me exceedingly defensive. I trained on Active Directory (AD) with a group of veteran sysadmins in 1999. I don't have access to the "Microsoft Official Curriculum" book from my class in '99 (long-since thrown away), but I have a distinct memory of a lively conversation in class re: the pitfalls of using a public domain name as…

Microsoft has provided mechanisms for split-horizon DNS service since Server 2003. views are not the only way of providing split-horizon DNS service.

* http://jdebp.info./FGA/dns-split-horizon.html#SeparateConten...

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

#798

Post by JdeBP »

brodo wrote: post #700
EvanAnderson wrote: post #533

Earlier quoted context omitted.

This one is kind of a "religious" topic for me, I guess. I'm sorry that it is, but it makes me exceedingly defensive. I trained on Active Directory (AD) with a group of veteran sysadmins in 1999. I don't have access to the "Microsoft Official Curriculum" book from my class in '99 (long-since thrown away), but I have a distinct memory of a lively conversation in class re: the pitfalls of using a public domain name as…

I don’t know anything about AD, so this might be a stupid question: can you not just run a web server on the same host as the AD server or port forward all HTTP traffic to a different server?

A domain controller on the internal network might not be the right place to run a copy of the public-facing content HTTP server (which might be in a datacentre, or even managed and run by an outside party, and might not be served by IIS). Then there are considerations of firewalling rules, browser rules, anti-virus rules, and even DNS rules for machines on the internal network that access a public WWW site that DNS lookups map into non-public IP addresses. (To prevent certain forms of external attacks, system administrators have taken in recent years to preventing this very scenario from working by filtering DNS results.)

* http://jdebp.eu./FGA/dns-split-horizon-common-server-names.h...

* http://jdebp.eu./FGA/dns-ms-dcs-overwrite-domain-name.html

* http://jdebp.eu./FGA/dns-use-domain-names-that-you-own.html

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

#800

Post by snsr »

lucideer wrote: post #789

Even if you believe this is in theory a good idea, in practice it's clear that Chrome has implemented this extremely badly. As Comment 5 on that issue points out: > This does appear to be inconsistent/improperly implemented. Why is www hidden twice if the domain is "www.www.2ld.tld"? [...] If the root zone is a 301 to the "www" version, removing "www" from the omnibox would be acceptable since the server indicated th…

Even dumber, from another comment-

> Another case I ran into:

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

Post reply on HN