X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fconfig.html;h=532657350d8820798c2d798d7931d3fdd5bb1a69;hp=ad8e518e7856b5db52832501452c14c1f4e0c7ae;hb=3f970a064dc22c089ae2e9c78ef7ce8539908bdd;hpb=304265caf6f5074df69e69282e5f33bb8aedade5 diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html index ad8e518e..53265735 100644 --- a/doc/webserver/user-manual/config.html +++ b/doc/webserver/user-manual/config.html @@ -4,7 +4,7 @@
Privoxy 3.0.29 User Manual | +Privoxy 3.0.30 User Manual | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prev | @@ -547,10 +547,10 @@
- debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. +debug 1 # Log the destination for each request. See also debug 1024. debug 2 # show each connection status - debug 4 # show I/O status + debug 4 # show tagging-related messages debug 8 # show header parsing debug 16 # log all data written to the network debug 32 # debug force feature @@ -689,10 +689,13 @@ enforce-blocks 1 If your system implements RFC 3493, then src_addr and dst_addr can be - IPv6 addresses delimeted by brackets, port can be a number or a + IPv6 addresses delimited by brackets, port can be a number or a service name, and src_masklen and dst_masklen can be a number from 0 to 128. @@ -1382,8 +1385,8 @@
Client-specific tags allow Privoxy admins to create different profiles and let the users chose which one they want without impacting other users. One use case is allowing users to circumvent certain blocks without having to allow them to circumvent @@ -2230,7 +2222,7 @@ 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. + understands the effect of the tag.# Define a couple of tags, the described effect requires action sections # that are enabled based on CLIENT-TAG patterns. client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions - disable-content-filters Disable content-filters 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
-
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 that is the result of an overly-broad URL pattern. The CGI interface http://config.privoxy.org/client-tags therefore provides a "enable this tag temporarily" option. If it is used, the tag will be set until the client-tag-lifetime is over.
If clients reach Privoxy through another proxy, for example a load balancer, Privoxy can't tell the client's IP address from the connection. If multiple clients use the same proxy, they will share the same client tag settings which is usually not desired. @@ -2341,7 +2314,7 @@ change the client tags for other clients or increase Privoxy's memory requirements by registering lots of client tag settings for clients that don't exist.
certificate-directory /usr/local/var/privoxy/certs
-
+ 7.7.6. trusted-cas-file+7.7.6. cipher-list+
+
+
+ 7.7.7. trusted-cas-file
|