Bug #128


Cannot enter host-only URLs, searches instead

Added by azr dev almost 7 years ago. Updated about 5 years ago.

Next Release
Start date:
Due date:
% Done:


Estimated time:


I try to access a server by hostname which does not have a FQDN (i.e. a domain). Instead of opening the site, privacy browser always sends my hostname to the search engine (which is not where I want to go and bad privacy-wise, too).
I tried the host itself "mynas", with trailing slash or path "mynas/", with protocol prefix "http://mynas" or port "http://mynas:80/", "mynas:80", to no avail. Access by IP works, though.

Also, when such a non-qualified URL occurs in a link on a website, it's opened just fine.

Actions #1

Updated by Soren Stoutner almost 7 years ago

  • Status changed from New to Closed
  • Assignee set to Soren Stoutner

This was indeed a problem with the logic that decides whether to load a URL or perform a search. That is why it only affected URLs loaded from the URL text box and not links (or bookmarks).

This bug has been fixed in;a=commitdiff;h=6f1b0c12fcf3358c91f7b5889a1dfe083638cb52, which will be included in Privacy Browser 2.3.

The new logic loads a URL for any FQDN, as well as any string that begins with `http://` or `https://`. Thus, `http://mynas` and `https://mynas` will load the URL, but `mynas`, and `mynas/` will perform a search.

With this change, the previous behavior of loading a URL for any string containing `localhost` has been removed. Thus, `http://localhost` and `https://localhost` will load the URL, but `localhost` will perform a search.

Actions #2

Updated by Soren Stoutner about 5 years ago

  • Priority changed from 2 to Next Release

Also available in: Atom PDF