From: Fabian Keil Date: Sat, 27 Jan 2007 13:13:44 +0000 (+0000) Subject: - Add config file entries for "templdir", X-Git-Tag: v_3_0_7~356 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=f22c831e83ba632c3b5ba23912c6f96d4aec7419;ds=sidebyside - Add config file entries for "templdir", "accept-intercepted-requests" and "split-large-forms". - Update meaning of debug 128 which is used by all redirecting actions now. --- diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 69efcb61..90369627 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.11 2006/09/08 02:36:37 hal9 Exp $ + $Id: p-config.sgml,v 2.12 2006/09/22 01:27:55 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org + Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org See LICENSE. ======================================================================== @@ -95,7 +95,7 @@ Sample Configuration File for Privoxy v&p-version; - $Id: p-config.sgml,v 2.11 2006/09/08 02:36:37 hal9 Exp $ + $Id: p-config.sgml,v 2.12 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org @@ -540,6 +540,50 @@ II. FORMAT OF THE CONFIGURATION FILE @@confdir .]]> + +templdir + + + + Specifies: + + An alternative directory where the templates are loaded from + + + + Type of value: + + Path name + + + + Default value: + + unset + + + + Effect if unset: + + The templates are assumed to be located in confdir/template. + + + + Notes: + + + Privoxy's original templates are usually overwritten + with each update. Use this option to relocate customized templates + that should be kept. Note that you might be missing new features + if you use outdated templates. + + + + + +@@#templdir .]]> + + logdir @@ -1000,7 +1044,7 @@ actionsfile debug 16 # log all data into the logfile debug 32 # debug force feature debug 64 # debug regular expression filter - debug 128 # debug fast redirects + debug 128 # debug redirects debug 256 # debug GIF de-animation debug 512 # Common Log Format debug 1024 # debug kill pop-ups @@ -1963,7 +2007,7 @@ forward-socks4 and forward-socks4a forwarded-connect-retries is mainly interesting - for socks4a connections, where Privoxy can't detect why the connections failed. + for socks4a connections, where Privoxy can't detect why the connections failed. The connection might have failed because of a DNS timeout in which case a retry makes sense, but it might also have failed because the server doesn't exist or isn't reachable. In this case the retry will just delay the appearance of Privoxy's error message. @@ -1987,6 +2031,136 @@ forward-socks4 and forward-socks4a @@forwarded-connect-retries 0]]> +accept-intercepted-requests + + + Specifies: + + + Whether intercepted requests should be treated as valid. + + + + + Type of value: + + + 0 or 1 + + + + + Default value: + + 0 + + + + Effect if unset: + + + Only proxy requests are accepted, intercepted requests are treated as invalid. + + + + + Notes: + + + If you don't trust your clients and want to force them + to use Privoxy, enable this + option and configure your packet filter to redirect outgoing + HTTP connections into Privoxy. + + + Make sure that Privoxy's own requests + aren't redirected as well. Additionally take care that + Privoxy can't intentionally connect + to itself, otherwise you could run into redirection loops if + Privoxy's listening port is reachable + by the outside or an attacker has access to the pages you visit. + + + + + Examples: + + + accept-intercepted-requests 1 + + + + +@@accept-intercepted-requests 0]]> + + +split-large-forms + + + Specifies: + + + Whether the CGI interface should stay compatible with broken HTTP clients. + + + + + Type of value: + + + 0 or 1 + + + + + Default value: + + 0 + + + + Effect if unset: + + + The CGI form generate long GET URLs. + + + + + Notes: + + + Privoxy's CGI forms can lead to + rather long URLs. This isn't a problem as far as the HTTP + standard is concerned, but it can confuse clients with arbitrary + URL lenght limitations. + + + Enabling split-large-forms causes Privoxy + to devide big forms into smaller ones to keep the URL length down. + It makes editing a lot less convenient and you can no longer + submit all changes at once, but at least it works around this + browser bug. + + + If you don't notice any editing problems, there is no reason + to enable this option, but if one of the submit buttons appears + to be broken, you should give it a try. + + + + + Examples: + + + split-large-forms 1 + + + + +@@split-large-forms 0]]> + +