X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=b379c72fcc536ccbd9c2bbbf1b128f154fc6e331;hb=ec4a051cd6a42c47dd9cf2fec9a1ab179649c6d5;hp=1ae21de644cd21bb1f9fbd7710c64ee34ddae672;hpb=8ef9b6820a17058776dc5aa8815ae44490342a25;p=privoxy.git diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 1ae21de6..b379c72f 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3,9 +3,9 @@ Purpose : Used with other docs and files only. - $Id: p-config.sgml,v 2.112 2014/11/28 14:26:35 fabiankeil Exp $ + $Id: p-config.sgml,v 2.120 2016/04/04 10:56:35 fabiankeil Exp $ - Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/ + Copyright (C) 2001-2016 Privoxy Developers https://www.privoxy.org/ See LICENSE. ======================================================================== @@ -97,10 +97,10 @@ Sample Configuration File for Privoxy &p-version; - $Id: p-config.sgml,v 2.112 2014/11/28 14:26:35 fabiankeil Exp $ + $Id: p-config.sgml,v 2.120 2016/04/04 10:56:35 fabiankeil Exp $ -Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/ +Copyright (C) 2001-2016 Privoxy Developers https://www.privoxy.org/ @@ -229,7 +229,7 @@ II. FORMAT OF THE CONFIGURATION FILE Effect if unset: - http://www.privoxy.org/version/user-manual/ + https://www.privoxy.org/version/user-manual/ will be used, where version is the Privoxy version. @@ -316,7 +316,7 @@ II. FORMAT OF THE CONFIGURATION FILE -@@#user-manual http://www.privoxy.org/user-manual/]]> +@@#user-manual https://www.privoxy.org/user-manual/]]> @@ -2478,6 +2478,12 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Privoxy's listening port is reachable by the outside or an attacker has access to the pages you visit. + + If you are running Privoxy as intercepting proxy without being + able to intercept all client requests you may want to adjust + the CGI templates to make sure they don't reference content from + config.privoxy.org. + @@ -3350,6 +3356,156 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t +client-specific-tag + + + Specifies: + + + The name of a tag that will always be set for clients that + requested it through the webinterface. + + + + + Type of value: + + + Tag name followed by a description that will be shown in the webinterface + + + + + Default value: + + None + + + + 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 + impacting other users. + + + One use case is allowing users to circumvent certain blocks + without having to allow them to circumvent all blocks. + This is not possible with the + enable-remote-toggle feature + because it would bluntly disable all blocks for all users and also affect + other actions like filters. + It also is set globally which renders it useless in most multi-user setups. + + + After a client-specific tag has been defined with the client-specific-tag + directive, action sections can be activated based on the tag by using a + CLIENT-TAG pattern. + The CLIENT-TAG pattern is evaluated at the same priority + as URL patterns, as a result the last matching pattern wins. + Tags that are created based on client or server headers are evaluated + later on and can overrule CLIENT-TAG and URL patterns! + + + The tag is set for all requests that come from clients that requested + it to be set. + Note that "clients" are differentiated by IP address, + if the IP address changes the tag has to be requested again. + + + 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. + + + + + Examples: + + + + # 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-tag-lifetime + + + Specifies: + + + How long a temporarily enabled tag remains enabled. + + + + + Type of value: + + + Time in seconds. + + + + + Default value: + + 60 + + + + 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 + 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. + + + + + Examples: + + + + # Increase the time to life for temporarily enabled tags to 3 minutes + client-tag-lifetime 180 + + + + + + +