ipfsContent.js prevents connecting to all websites under certain conditions

[eduadiez]

Describe the bug
With the current implementation of ipfsContent.js all requests are listened even of the type xmlhttprequest, websockets, ...

I think the current implementation is too invasive, and it may turn out that if you use a .eth as a metamask provider and the connection is lost you won't be able to access to any website (neither .eth nor any other TLD)

Example:

21:36:17.461 console.js:35 {error: "net::ERR_NAME_NOT_RESOLVED", frameId: 0, fromCache: false, initiator: "http://mycrypto.dappnode.eth", method: "OPTIONS", …}error: "net::ERR_NAME_NOT_RESOLVED"frameId: 0fromCache: falseinitiator: "http://mycrypto.dappnode.eth"method: "OPTIONS"parentFrameId: -1requestId: "7600"tabId: 1345496486timeStamp: 1539027377460.8418type: "xmlhttprequest"url: "http://my.ethchain.dnp.dappnode.eth:8545/"__proto__: Object

Although this commit can partially fix the problem, it only solves it in case of using a port in the url

I think it should use webRequest.RequestFilter to filter only main_frame the request.

[eduadiez]

I just made a PR to fix this problem #5461