Issue 1727 - Prevent circumvention via WebSocket

background.js

Index: background.js
diff --git a/background.js b/background.js
index 3e2eb08be89145c56ce79fe3ad3d676b8a4655dd..971f7a2838d84c3f5a116b8de65bd7bcda88fc6f 100644
--- a/background.js
+++ b/background.js
@@ -41,6 +41,17 @@ port.on("get-selectors", function(msg, sender)
   return {selectors: selectors, trace: trace};
 });
 
+port.on("websocket-request", function(msg, sender)

[Sebastian Noack, 2016/06/28 16:17:51]

Please no new code in background.js. This file is matter to be removed. And this
seems to rather belong in requestBlocker.js anyway.

[kzar, 2016/06/29 13:40:30]

Done.

+{
+  var results = ext.webRequest.onBeforeRequest._dispatch(
+    new URL(msg.url),

[Sebastian Noack, 2016/06/28 16:17:51]

Is it possible to create a WebSocket with a relative URL? Then we'd have to make
sure to pass the corresponding base URL to the URl() constructor here.

[kzar, 2016/06/29 13:40:30]

No, I don't believe it's possible. (I see an exception when attempting to do
it.)

[lainverse, 2016/06/29 13:54:58]

As I understood you must pass FQDN URL. At least for now. Neither Chrome, nor
Firefox supports relative URLs and there are a lot of questions on the web
regarding this with the same answer to generate a full URL.

[Sebastian Noack, 2016/07/01 17:03:39]

Ah right. Of course it needs to be an absolute URL because it's a different
protocol anyway.

+    "OTHER",
+    sender.page,
+    sender.frame
+  );
+  return results.indexOf(false) != -1;
+});
+
 port.on("forward", function(msg, sender)
 {
   var targetPage;