Why did you mark this as security sensitive? (In reply to Sagar from comment #8) > @mak `browser.fixup.domainwhitelist.go` wont help me much because `go` isn't the only keyword they redirect with. there's also `c/foo` for calendar of user `foo`, for example. There's a litany of these. You can create how many prefs as you wish of course, and I'd suggest using an autoconfig file to avoid doing that manually. Of course in an enterprise it's simpler to rely on the dns... > `browser.fixup.dns_first_for_single_words` might work out, but since it worked without a flag switch before, is this considered a regression? > And will that flag go away anytime soon? (If we do start relying on that workaround...) It's not a regression, we changed the behavior on purpose because the old behavior was confusing users, and was also not coherent with any other browser. The browser.fixup.dns_first_for_single_words flag won't go away, it's largely used by enterprises. > Especially since other browsers (Edge/Chrome) work, but yeah Safari doesn't (redirects to search unless I append a `/` like `c/foo/`) From Firefox 78 you can also force a visit appending a slash, though with one of the previous solutions that won't be necessary.
Bug 1642435 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Why did you mark this as security sensitive? (In reply to Sagar from comment #8) > @mak `browser.fixup.domainwhitelist.go` wont help me much because `go` isn't the only keyword they redirect with. there's also `c/foo` for calendar of user `foo`, for example. There's a litany of these. You can create how many prefs as you wish of course, and I'd suggest using an autoconfig file to avoid doing that manually. Of course in an enterprise environment with many intranet domains not using suffixes, it's simpler to rely on the dns... > `browser.fixup.dns_first_for_single_words` might work out, but since it worked without a flag switch before, is this considered a regression? > And will that flag go away anytime soon? (If we do start relying on that workaround...) It's not a regression, we changed the behavior on purpose because the old behavior was confusing users, and was also not coherent with any other browser. The browser.fixup.dns_first_for_single_words flag won't go away, it's largely used by enterprises. > Especially since other browsers (Edge/Chrome) work, but yeah Safari doesn't (redirects to search unless I append a `/` like `c/foo/`) From Firefox 78 you can also force a visit appending a slash, though with one of the previous solutions that won't be necessary.