From bcf9e5ef9fb69a353a9d46a6122641c9edd2430b Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 25 Jan 2015 10:01:23 -0500 Subject: [PATCH] Updated Behind the scene network requests (markdown) --- Behind-the-scene-network-requests.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Behind-the-scene-network-requests.md b/Behind-the-scene-network-requests.md index c11c817..0627473 100644 --- a/Behind-the-scene-network-requests.md +++ b/Behind-the-scene-network-requests.md @@ -34,6 +34,8 @@ To access the filtering settings for the behind-the-scene network requests is si ![Behind-the-scene popup](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/behind-the-scene-popup.gif)
The popup UI will be filled with the data of whatever tab is being currently inspected in the request logger. -**Important:** Filter behind-the-scene requests at your own risk. I will close without further comment any reported issue which are a direct consequence of blocking behind-the-scene network requests. +The picture above shows what happen when you browser Github: Github makes use of `navigator.sendBeacon()` to send data to Google Analytics, which results in the firing of behind-the-scene requests in Chromium browser. +**Important:** Filter behind-the-scene requests at your own risk. I will close without further comment any reported issue which are a direct consequence of blocking behind-the-scene network requests. Remember that if you block indiscriminately, you could cripple the ability of your browser to update extensions, ability of extensions to work properly, etc. This is why this is deemed an advanced user feature. + To turn off the filtering of behind-the-scene requests is just a matter of whitelisting the _"Behind the scene"_ scope, or to turn off _"advanced user"_ mode. \ No newline at end of file