From 1600208c75a3458bb803717dc94ec5668a857033 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Thu, 19 Oct 2017 10:50:11 -0400 Subject: [PATCH] Updated Dashboard: Settings (markdown) --- Dashboard:-Settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dashboard:-Settings.md b/Dashboard:-Settings.md index a1d3f61..76a6eb3 100644 --- a/Dashboard:-Settings.md +++ b/Dashboard:-Settings.md @@ -90,7 +90,7 @@ Consider this excerpt from [Reporting API / Privacy Considerations](http://wicg. There is currently no way to easily toggle CSP reporting in either Chromium of Firefox. This per-site switch is to address this shortcoming. -Note that as opposed to all other network requests, behind-the-scene network requests which are actual CSP reports will also be filtered out according to `no-csp-reports` switch. So if you globally disable CSP reporting in uBO, this will also apply to behind-the-scene network requests. +Note that as opposed to all other network requests, behind-the-scene network requests which are actual CSP reports will also be filtered out according to this setting. So if you globally disable CSP reporting in uBO, this will also apply to behind-the-scene network requests. Note that the blocking of CSP reports is implemented as a per-site switch internally in uBO, so this means that an advanced user could create rules in the _My rules_ pane in the dashboard to allow a more granular control of the blocking of CSP reports. For example: