Live data from Hacker News

Chromium uses web search for .internal TLD instead of opening URL

issues.chromium.org

11–20 of 96 posts

Re: Chromium uses web search for .internal TLD instead of opening URL

#11
From TFA:

    Resolved (2024.07.29.06), the Board [ICANN] reserves .INTERNAL from delegation in the DNS root zone permanently to provide for its use in private-use applications. The Board recommends that efforts be undertaken to raise awareness of its reservation for this purpose through the organization's technical outreach

Re: Chromium uses web search for .internal TLD instead of opening URL

#13

I find auto-complete adding to this annoying behavior. It's (nearly) broken the 'view-source:' functionality in Chrome on Android

it's the deliberate dumbing down of the computer to the ordinary user, in the name of ease of use.

Whether intentional malice, or unintentional incompetence is moot by now. The effect has already been done.

Re: Chromium uses web search for .internal TLD instead of opening URL

#15

Can’t you usually force it to skip the search by prefixing with the schema? Certainly if I type in http://example.internal and press enter, I would be very displeased to have that turn into a Google search regardless of whether the part after the // fits some regex or whatever else internal to the browser.

Right, considering that single-label names (indistinguishable from search queries) have been a thing since WINS/NetBIOS, DHCP suffixing, etc. -- expecting a dot (let alone a dot followed by a public suffix) is bogus.

Re: Chromium uses web search for .internal TLD instead of opening URL

#17
post #4

One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?

I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to.

But I use firefox and I turned off autocomplete. And I use my own search instance (SearXNG)

Re: Chromium uses web search for .internal TLD instead of opening URL

#18
post #2

Having trouble not attributing to malice that which is adequately explained by stupidity here... For Home Assistant for instance, the only reasonable option is .internal - its default .local is not the right TLD to use. [1] [1]: https://serverfault.com/a/937808

Isn't .local specific to 'rendezvous' tech anyway? I forget the generic name but it was Apple that put it on the map under this name. But I mean that serverless broadcast protocol.

What I do is I just bought a domain and use that together with DNS-based SSL. It's a bit hard to set up with every different SSL server but it's doable.

Post reply on HN