From 86f4ed42c5c2314ecbc5b765374c2c4e23a18bd6 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Wed, 6 Sep 2006 11:38:33 +0000 Subject: [PATCH] Added sections for enable-remote-http-toggle and forwarded-connect-retries. --- doc/source/p-config.sgml | 119 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 117 insertions(+), 2 deletions(-) diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 5c02fefb..8223117d 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3,7 +3,7 @@ Purpose : Used with other docs and files only. - $Id: p-config.sgml,v 2.7 2006/09/04 18:09:06 hal9 Exp $ + $Id: p-config.sgml,v 2.8 2006/09/06 02:17:53 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers See LICENSE. @@ -95,7 +95,7 @@ Sample Configuration File for Privoxy v&p-version; - $Id: p-config.sgml,v 2.7 2006/09/04 18:09:06 hal9 Exp $ + $Id: p-config.sgml,v 2.8 2006/09/06 02:17:53 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org @@ -1275,6 +1275,60 @@ actionsfile + +enable-remote-http-toggle + + + Specifies: + + + Whether or not Privoxy recognizes special HTTP headers to change its behaviour. + + + + + Type of value: + + 0 or 1 + + + + Default value: + + 1 + + + + Effect if unset: + + + Privoxy ignores special HTTP headers. + + + + + Notes: + + + When toggled on, the client can change Privoxy's + behaviour by setting special HTTP headers. Currently the only supported + special header is X-Filter: No, to disable filtering for + the ongoing request, even if it is enabled in one of the action files. + + + If you are using Privoxy in a + multi-user environment or with untrustworthy clients and want to + enforce filtering, you will have to disable this option, + otherwise you can ignore it. + + + + + +@@enable-remote-http-toggle 1]]> + + + enable-edit-actions @@ -1847,6 +1901,67 @@ forward-socks4 and forward-socks4a ]]> +forwarded-connect-retries + + + Specifies: + + + How often Privoxy retries if a forwarded connection request fails. + + + + + Type of value: + + + Number of retries. + + + + + Default value: + + 0 + + + + Effect if unset: + + + Forwarded connections are treated like direct connections and no retry attempts are made. + + + + + Notes: + + + forwarded-connect-retries is mainly interesting + 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. + + + Only use this option, if you are getting many forwarding related error messages, + that go away when you try again manually. Start with a small value and check Privoxy's + logfile from time to time, to see how many retries are usually needed. + + + + + Examples: + + + forwarded-connect-retries 1 + + + + +@@forwarded-connect-retries 0]]> + + -- 2.39.2