From 79f94634e633f6e62aa79a355e31f71463f2b1d1 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 23 Mar 2015 07:50:13 -0400 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 2547ef3..df7a56d 100644 --- a/Behind-the-scene-network-requests.md +++ b/Behind-the-scene-network-requests.md @@ -38,7 +38,9 @@ To access the filtering settings for the behind-the-scene network requests is si The picture above shows what happen when you navigate through 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 is 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. +**Important:** Filter behind-the-scene requests at your own risk. I will close without further comment any reported issue which is 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 parts of itself properly, ability 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.