X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=b0ab50f240f2bae2a55be9224dcd0b3e0a2ff512;hb=c602d314c0fdf8093d606570bee796fc2f520af9;hp=f8bae1d5fc2b24d35e45abc17c14d79eac07c251;hpb=b38efc2474f216ae3df7d876d4e18780b4c532fe;p=privoxy.git
diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index f8bae1d5..b0ab50f2 100644
--- a/doc/source/p-config.sgml
+++ b/doc/source/p-config.sgml
@@ -738,6 +738,7 @@ actionsfile
fk 2007-11-07
-->
@@actionsfile user.action # User customizations]]>
+@@#regression-tests.action # Tests for privoxy-regression-test]]>
@@ -1269,7 +1270,7 @@ actionsfile
They can only be used if Privoxy has
been compiled with IPv6 support. If you aren't sure if your version
supports it, have a look at
- http://config.privoxy.org/show-status.
+ http://config.privoxy.org/show-status.
Some operating systems will prefer IPv6 to IPv4 addresses even if the
@@ -3632,12 +3633,6 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
Notes:
-
-
- This is an experimental feature. The syntax is likely to change
- in future versions.
-
-
Client-specific tags allow Privoxy admins to create different
profiles and let the users chose which one they want without
@@ -3671,7 +3666,7 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
Clients can request tags to be set by using the CGI interface http://config.privoxy.org/client-tags.
The specific tag description is only used on the web page and should
- be phrased in away that the user understand the effect of the tag.
+ be phrased in away that the user understands the effect of the tag.
@@ -3683,6 +3678,11 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
# that are enabled based on CLIENT-TAG patterns.
client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions
client-specific-tag disable-content-filters Disable content-filters but do not affect other actions
+ client-specific-tag overrule-redirects Overrule redirect sections
+ client-specific-tag allow-cookies Do not crunch cookies in either direction
+ client-specific-tag change-tor-socks-port Change forward-socks5 settings to use a different Tor socks port (and circuits)
+ client-specific-tag no-https-inspection Disable HTTPS inspection
+ client-specific-tag no-tls-verification Don't verify certificates when http-inspection is enabled
@@ -3718,12 +3718,6 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
Notes:
-
-
- This is an experimental feature. The syntax is likely to change
- in future versions.
-
-
In case of some tags users may not want to enable them permanently,
but only for a short amount of time, for example to circumvent a block
@@ -3779,12 +3773,6 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
Notes:
-
-
- This is an experimental feature. The syntax is likely to change
- in future versions.
-
-
If clients reach Privoxy through another proxy, for example a load
balancer, Privoxy can't tell the client's IP address from the connection.
@@ -3904,9 +3892,11 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
HTTPS Inspection (Experimental)
- HTTPS inspection allows to filter encrypted requests.
+ HTTPS inspection allows to filter encrypted requests and responses.
This is only supported when Privoxy
has been built with FEATURE_HTTPS_INSPECTION.
+ If you aren't sure if your version supports it, have a look at
+ http://config.privoxy.org/show-status.
@@ -4084,6 +4074,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
The ca-cert-file section contains
a command to generate it.
+
+ Access to the key should be limited to Privoxy.
+