Bugzilla

I'm a little confused by the question.

The Unable to Connect page should only be expected in our specific case because we're "mocking" the existence of a single word that maps to an IP address for the purpose of testing that the preference works. By searching that word and landing on an "Unable to Connect" page instead of a search page, we've confirmed that the browser has found an IP address associated with the single word but wasn't able to connect to a server because I'm presuming on your machine you don't have something running at the address you provided for that keyword. 

We could for example start a server on localhost (e.g. via Node.js), map a single word like `cognizantsoftvision` to the same IP as localhost (like you've done in your hosts file), so that typing `cognizantsoftvision` would go to the page served by the server listening on localhost instead of showing an "Unable to Connect" page, but the outcome for our purposes would be the same, namely proving that the preference works.

If you are just generally curious about what circumstances "Unable to Connect" shows up, we can needsinfo someone on the networking team (e.g. Kershaw) to give more clarification.

I'm a little confused by the question.

The Unable to Connect page should only be expected in our specific case because we're "mocking" the existence of a single word that maps to an IP address for the purpose of testing that the preference works. By searching that word and landing on an "Unable to Connect" page instead of a search page, we've confirmed that the browser has found an IP address associated with the single word but wasn't able to connect to a server because I'm presuming on your machine you don't have something running at the address you provided for that keyword. 

We could for example start a server on localhost (e.g. via Node.js), map a single word like `cognizantsoftvision` to the same IP as localhost (like you've done in your hosts file), so that typing `cognizantsoftvision` would go to the page served by the server listening on localhost instead of showing an "Unable to Connect" page, but the outcome for our purposes would be the same, namely proving that the preference works. If you'd like, I can set up a Github repo with a super basic Node server setup, so that you would download the repo, run it locally on localhost, and provided you map the address correctly in your hosts file, should expect to see the result from the Node server instead of a search result.

If you are just generally curious about what circumstances "Unable to Connect" shows up, we can needsinfo someone on the networking team (e.g. Kershaw) to give more clarification.