Closed Bug 1799155 Opened 3 years ago Closed 3 years ago

Hostname not recognized in address bar

Categories

(Firefox :: Address Bar, defect)

Firefox 106
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: private, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

Enter a hostname with a 1 letter TLD in the address bar (ie. "some-server.a")

Actual results:

The input was interpreted as search request

Expected results:

To my knowledge 1 letter TLDs are valid TLDs. So "some-server.a" is a perfectly valid hostname. Therefore Firefox should issue a http/https request to that server and not search for the server name using the selected search engine.

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Address Bar

(In reply to private from comment #0)

Enter a hostname with a 1 letter TLD in the address bar (ie. "some-server.a")

.a is not in the PSL (public suffix list), you likely defined it in your network and it's not widely used, so we default to a search.
To support your use-case, you can do one of these things:

  1. use a more widely supported suffix, like .local, .internal or .test instead of .a
  2. add your .a suffix to the allowlist, by going to about:support and creating a new BOOLEAN pref named browser.fixup.domainsuffixwhitelist.a and set it to true
  3. ask Firefox to check the dns first (setting browser.fixup.dns_first_for_single_words to true in about:config), though this will make searches slower because we'll have to hit the dns every time to make a decision

We don't plan to fix this, because we think the current behavior is the best compromise and with a couple prefs you can customize it to your needs.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX

Technically speaking all your suggested TLDs are not valid for local use for different reasons:

Only one letter TLDs are exempt from becoming public TLDs, for my network it's .i for "internal".

I appreciate your tips and will check which one works best but I still fail to understand how a modern browser is not able to access a perfectly valid URL when entered in the address bar. This is something that shouldn't happen.

You need to log in before you can comment on or make changes to this bug.