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

#1

Post by nh2 » Thu, Oct 24, 2024, 1:19 AM UTC

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

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

#2

Post by racked » Thu, Oct 24, 2024, 3:09 AM UTC

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

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

#3

Post by mikepurvis » Thu, Oct 24, 2024, 3:13 AM UTC

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.

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

#4

Post by exabrial » Thu, Oct 24, 2024, 3:19 AM UTC

One of the worst security bugs of browsers is the combined url/search bar. But Google loves it!

What about .corp subdomains?

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

#5

Post by [deleted] » Thu, Oct 24, 2024, 3:25 AM UTC

racked wrote: 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