| Privoxy 3.0.28 User Manual | +Privoxy 3.0.30 User Manual | |||||||
|---|---|---|---|---|---|---|---|---|
| Prev | @@ -73,7 +73,7 @@||||||||
+ # Remove "test" everywhere in the request body
+{+client-body-filter{remove-test}}
+/
+ |
+
To detect a redirection URL, fast-redirects only looks for the string "http://", either in plain text (invalid but often used) or encoded as "http%3a//". Some sites use their own URL encoding scheme, encrypt the address - of the target server or replace it with a database id. In theses cases fast-redirects is fooled and the request reaches the redirection server where it probably gets logged.
@@ -1546,7 +1604,7 @@ problem-host.example.com"Rolling your own" filters requires a knowledge of "Regular - Expressions" and "Regular + Expressions" and "HTML". This is very powerful feature, and potentially very intrusive. Filters should be used with caution, and where an equivalent "action" is not available.
-The amount of data that can be filtered is limited to the The amount of data that can be filtered is limited by the buffer-limit option in the main config file. The default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered data, and all pending data, is passed through unfiltered.
@@ -1820,6 +1878,15 @@ problem-host.example.com
+ +filter{github} # Removes the annoying "Sign-Up" banner and the Cookie disclaimer.
+ |
+
+ +filter{imdb} # Removes some ads on IMDb.
+ |
+
+ +filter{sourceforge} # Reduces the amount of ads for proprietary software on SourceForge.
+ |
+
More information on known user-agent strings can be found at http://www.user-agents.org/ and http://www.user-agents.org/ and http://en.wikipedia.org/wiki/User_agent.
- +hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}
+ +hide-user-agent{Mozilla/5.0 (X11; ElectroBSD i386; rv:78.0) Gecko/20100101 Firefox/78.0}
|
Filter encrypted requests and responses
+Encrypted requests are decrypted, filtered and forwarded encrypted.
+Boolean.
+N/A
+This action allows Privoxy to filter encrypted requests and + responses. For this to work Privoxy has to generate a certificate and + send it to the client which has to accept it.
+Before this works the directives in the HTTPS inspection section of the config + file have to be configured.
+Note that the action has to be enabled based on the CONNECT request which doesn't contain a path. + Enabling it based on a pattern with path doesn't work as the path is only seen by Privoxy if the action is already enabled.
+This is an experimental feature.
+
+ {+https-inspection}
+www.example.com
+ |
+
Filter encrypted requests and responses without verifying the certificate
+Encrypted requests are forwarded to sites without verifying the certificate.
+Boolean.
+N/A
+When the "+https-inspection" action is used Privoxy by default + verifies that the remote site uses a valid certificate.
+If the certificate can't be validated by Privoxy the connection is + aborted.
+This action disables the certificate check so requests to sites with certificates that can't be + validated are allowed.
+Note that enabling this action allows Man-in-the-middle attacks.
+
+ {+ignore-certificate-errors}
+ www.example.org
+
+ |
+
Note that some (rare) ill-configured sites don't handle requests for uncompressed documents correctly. Broken PHP applications tend to send an empty document body, some IIS versions only send the beginning of - the content. If you enable prevent-compression per default, you might want to - add exceptions for those sites. See the example for how to do that.
+ the content and some content delivery networks let the connection time out. If you enable prevent-compression per default, you might want to add exceptions for those sites. See the + example for how to do that.Suppress client or server tag.
+Server or client tags to which this action applies are not added to the request, thus making all + actions that are specific to these request tags inactive.
+Multi-value.
+The result tag of a server-header or client-header tagger, as defined in one of the filter files.
+
+ # Suppress tag produced by range-requests client-header tagger for requests coming from address 10.0.0.1
+{+suppress-tag{RANGE-REQUEST}}
+TAG:^IP-ADDRESS: 10\.0\.0\.1$
+ |
+
Note that many of these actions have the potential to cause a page to misbehave, possibly even not to display at all. There are many ways a site designer may choose to design his site, and what HTTP header content, and other criteria, he may depend on. There is no way to have hard and fast rules for all sites. See