From bb6e635c61a4847b7445b4359d212744fff8cb6f Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 23 Mar 2015 07:56:48 -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 df7a56d..f8ef4e1 100644 --- a/Behind-the-scene-network-requests.md +++ b/Behind-the-scene-network-requests.md @@ -44,4 +44,6 @@ Remember that if you block indiscriminately, you could cripple the ability of yo 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. -To whitelist the behind-the-scene scope: add `behind-the-scene` as a whitelist directive, in the _Whitelist_ tab of µBlock's dashboard. \ No newline at end of file +To whitelist the behind-the-scene scope: add `behind-the-scene` as a whitelist directive, in the _Whitelist_ tab of µBlock's dashboard. + +If there are only very specific behind-the-scene network requests you would like to filter, a good approach to minimize potential problems is to use dynamic filtering: set a local rule for the `all` cell to _allow_ (green) (i.e. `behind-the-scene * * allow`). This will ensure nothing is blocked in the behind-the-scene scope, just as if uBlock is disabled for that scope. Then proceed to create _block_ rules for the specific hostnames for which you want to block all network requests. \ No newline at end of file