Firefox extension doesn't work without trailing slash

[icco]

In the firefox extension, go/jira goes to a search for go jira, go/jira/ goes to the right place.

[itsojon]

@icco thank you for creating this issue! Sorry you're running into this problem. Historically it has sufficed to open a go link with the explicit protocol once (e.g., "http://go/something") in order to teach Firefox that "go" is a hostname and not a search, which the extension should do programmatically on install. That approach doesn't seem to be reliably changing Firefox's behavior when I test it now though. Adding the trailing slash appears to also work as a signal to Firefox to treat the string as a URL.

We'll investigate further. While far from ideal, it looks like a reliable workaround is to go to about:config in Firefox and disable the keyword.enabled option.

[mikecarr]

The same with Safari

Version 15.2 (17612.3.6.1.6)

[danielktaylor]

about:config

browser.fixup.dns_first_for_single_words

set to true

[KyleJamesWalker]

Same issue on Vivaldi!

[zepatrik]

Another workaround with less side effects, that could also be implemented by the extension:

• add custom search engine with the URL https://go/%s using https://addons.mozilla.org/en-US/firefox/addon/add-custom-search-engine/
• add search keyword go/ (or any other you like) on about:preferences#search

[bendb-instacart]

For anyone who is stumbling across this years-old bug, there's another and cleaner browser-side fix:

1. Go to about:config
2. Search for browser.fixup.domainwhitelist.go, which won't exist but will show a plus button
3. Click the plus button to add a config, and leave it set to true

Now, you won't have to remember the extra / or type a protocol prefix.