Forum Discussion
Policy needed: "Go to an intranet site for a one-word entry in the Address bar"
- Aug 14, 2019
Thank you, ToMMeR, stesch79 and paf_skov for your feedback. I can appreciate those circumstances and your request.
We will look into adding a policy to make single-word queries navigate and I'll follow up on this thread with an update as soon as I have one.
Thanks again for giving us this important feedback and for describing your specific scenarios! It helps!Jared
JaredB81 Fantastic!
I have tested the implementation and it works as expected.
I have tried various combinations of single word entries, and entries with "." and "-".
If the word is not resolved in our DNS it instantly does as Google Search.
If the word exists as a hostname in our DNS, but no web server responds to the request, then it also redirects to a Google Search after timing out (which takes about 20 seconds). This is of course quite a long time to wait, but I think it is acceptable as if the word exists as a hostname in DNS you are most likely trying to access that web server and not search for the word.
I will continue to run on the this Edge Dev version with the feature enabled and let you know if i stumble upon anything unexpected. But I think it works as wished 🙂
Thank you for implementing this feature.
Thank you, ToMMeR, for testing our implementation and for confirming this policy now meets your needs, end-to-end, for your organization.
We will continue to monitor feedback from other members of the community and I would love to hear how others on this thread find the experience once they have done similar testing.
We will also continue to conduct internal testing to make sure navigating and searching work seamlessly when this policy is enabled. Once we have completed our testing and have heard from anyone else from the community who is testing the policy with the search fallback command-line flag enabled, we will remove the requirement to set the command-line flag. I’ll post an update on this thread when that takes place.
Finally, ToMMeR, I would be remiss as a member of the Address Bar and Search team to respond to your post without suggesting that you give Bing a try :-). Particularly with the new Microsoft Search in Edge feature which is designed to help members of your organization be even more productive, but with Bing relevance and performance improvements in general, we are working hard to make Bing the very best search experience in Microsoft Edge! Please give it a try – I’d love feedback on how Bing works for you as well :-).
Thanks very much,
Jared on behalf of the entire Address Bar and Search Team
- ToMMeRNov 15, 2019Brass Contributor
JaredB81 I have found a scenario where Edge does not react the way I intended/wished.
We have some internal websites that is using a self signed certificate not from our CA (Usually test systems, or appliances where it for some reason have been decided not to change the certificate).
This of course results in the "Your connection isn't private" (NET::ERR_CERT_AUTHORITY_INVALID) screen where you can then choose to continue even though it is "unsafe".
These systems do redirect to HTTPS if you try to access them on HTTP.
When trying to access one of these websites using just their hostname I very quickly see the redirect to HTTPS as i see the "Your connection isn't private" for a split second and then i am redirected to a search engine search.- Thilo LangbeinNov 22, 2019Iron Contributor
Does this work for Beta-Channel too?
- JaredB81Nov 22, 2019Iron Contributor
Thilo Langbein, the policy and most of the functionality enabled by this policy which this thread discusses is available in the Beta build. The fallback to search component of this policy is not yet in Beta. Once Beta moves over to the 80.x build numbers, it will get the fallback to search functionality. We expect Beta will move over to the 80.x build numbers closer to our release of the Stable channel (which is scheduled for 1/15/2020).
ToMMeR, thank you for the bug report. I have sent you a private message to get some more details about your specific issue. Please reply at your earliest convenience and we will look into it.
Thanks, everyone for the continued feedback and have a great weekend!
Jared and the entire Microsoft Edge Address Bar and Search Team