Metamask-extension: Remove ENS resolution on .test TLDs

[weijiekoh]

To Reproduce
Steps to reproduce the behavior:

1. In the command line, run google-chrome test.
2. The following screen will appear:

Expected behavior

The regular Google Chrome "This site can’t be reached" page.

Browser details (please complete the following information):

• OS: Ubuntu
• Browser: Chrome 68
• MetaMask Version 4.9.2

[whyrusleeping]

I get that same error trying to load phyrextsai.eth sometimes. Sometimes it works though (seems to work on the first time after a while, then fails repeatedly afterwards, feels like a caching issue)

[kumavis]

seems we're matching test instead of just *.test

[aertmann]

Why are you interfering with *.test in the first place? I use that for local development and it's a known pattern after Google bought the .dev TLD. Please find something more unique for your purpose.

[ZitRos]

Found this thing today. It is very strange, to be honest :) I agree that none of domain names should be intercepted (except of .eth possibly, if there's no such top-level domain exists).

Is there a place where this Metamask behavior is documented?

[bdresser]

This was originally included by the contributor as a convenience feature for debugging, but it's not too challenging to test your site on ropsten by loading the IPFS hash directly via a gateway.

We'll remove matching on .test domains in the next release. Thanks for the feedback!

[ZitRos]

@bitpshr, if you just enter eth in the address bar, it also causes the page to go to the "portal network"...