diff --git a/settings.html b/settings.html index abe47c9..2babb27 100644 --- a/settings.html +++ b/settings.html @@ -1,7 +1,8 @@ + -HTTP Switchboard — Settings +HTTP Switchboard — Settings + -

HTTP Switchboard — Settings

+

HTTP Switchboard — Settings

Under construction. @@ -34,7 +62,12 @@

Display

Strict blocking

-
+ +

Strict blocking, introduced in version 0.3.6, means that even @@ -47,13 +80,20 @@

Strict blocking

Strict blocking off: blacklisted types of request (if any) for a whitelisted hostname are allowed (unless you explicitly blacklist specifically these types of request for the whitelisted hostname.)

- -
+

Cookies

-
+ +

Blacklisted cookies are not prevented by HTTP Switchboard from entering your browser. However they are prevented from leaving your browser, which is what really matters. Not blocking cookies before they enter your browser @@ -61,17 +101,15 @@

Cookies

and furthermore to inspect their contents if you wish.

Once these blacklisted cookies have been accounted for by HTTP Switchboard, they can be removed from your browser if you wish so:

- -
+

Chromium: behind-the-scene requests

-
+ +

According to Google Chrome Privacy Whitepaper, Chromium might send HTTP requests to Google without the user expressly visiting a web page. Let's call these special requests @@ -81,9 +119,7 @@

Chromium: behind-the-scene requests

HTTP Switchboard let you intercept and treat these requests like any other request: they can be processed in order to allow/block them as per your whitelist/blacklist.

- +

Beware! Potentially blocking behind-the-scene net requests is currently causing an issue @@ -93,10 +129,12 @@

Chromium: behind-the-scene requests

installed extensions to not work properly (those querying for remote data).

Even if this feature is not enabled, behind-the-scene requests are still logged by HTTP Switchboard, so that you can at least inspect them - (from the Stats page). -

+ (from the Stats page). +

+
+ + + + - - - - +