From 0c49252de6c3a5420a5ef8b8be6c12cbd20a2094 Mon Sep 17 00:00:00 2001 From: gwarser Date: Tue, 10 Nov 2020 23:24:50 +0100 Subject: [PATCH] Updated Behind the scene network requests (markdown) --- Behind-the-scene-network-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Behind-the-scene-network-requests.md b/Behind-the-scene-network-requests.md index 434f342..c51aca3 100644 --- a/Behind-the-scene-network-requests.md +++ b/Behind-the-scene-network-requests.md @@ -6,7 +6,7 @@ This wiki page is out of date and in need of revision. When this documentation w Since then things have changed: uBO no longer can see network requests from other extensions, and behind-the-scene network requests are now quite less frequent. Furthermore, the webRequest API now provides more context to event listeners, such that it is often possible to still filter properly even when it's not possible to know from which exact tab a network request originates. -Because of this (and other reasons which will eventually come to light - the ["Who Left Open The Cookie Jar?"](https://github.com/ghacksuserjs/ghacks-user.js/issues/489) vulnerability), starting with uBO 1.15.20, the `behind-the-scene` scope will no longer be on trusted sites list by default, meaning network requests from the behind-the-scene scope will be subject to filtering by default. +Because of this (and other reasons which will eventually come to light - the ["Who Left Open The Cookie Jar?"](https://github.com/ghacksuserjs/ghacks-user.js/issues/489) vulnerability), starting with uBO 1.15.20, the `behind-the-scene` scope will no longer be on _Trusted sites_ list by default, meaning network requests from the behind-the-scene scope will be subject to filtering by default. ***