[Mozilla Enterprise] browser.fixup.dns_first_for_single_words works different?

[Peter Schlierf]

Dear all,

I found one difference in my tests between ESR 60 and ESR 68:

We use the setting:
pref("browser.fixup.dns_first_for_single_words", true)

This is to support for single words in address bar to first search for DNS and if nothing can be found it will search against your default search.
This worked well in ESR 60, if you entered an internal name without domain, which can be found in internal DNS it redirects to the website and did not search against your search provider (in our case Google). If the single word could not be resolved against internal DNS it searched for the word.

This behavior changed in ESR 68, if I now enter a single word in address bar for example: mysinglesearchword, it will search first against internal DNS, but if this is not successful it will try to open hardly the single word with www.mysinglesearchword.com<http://www.mysinglesearchword.com>. Attached screenshot shows this behavior.

If I set browser.fixup.dns_first_for_single_words to false, It will not happen, but then also the first scenario for internal DNS single words will not work.

Someone else using this feature or can explain the change?


Freundliche Grüße / Best regards,

Peter Schlierf
Front-End Engineering

////////////////////

Bayer Business Services GmbH
IT Operations – Workplace
Design & Build
E-mail:  peter.schlierf at bayer.com
Web:    http://www.business-services.bayer.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/enterprise/attachments/20190904/b63aa3f2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FF68Search.PNG
Type: image/png
Size: 87963 bytes
Desc: FF68Search.PNG
URL: <http://mail.mozilla.org/pipermail/enterprise/attachments/20190904/b63aa3f2/attachment.png>