X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=0e47644d809229ac1dc895a990d144502c2b63ce;hp=b25860fe32a0cdfe05fbe077b28f26e326974621;hb=f4107f65b676b63a199fe4230e58695757f9f199;hpb=573c8a27abc6c8df5bfd7ea90b5e4dcbac33151f
diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index b25860fe..0e47644d 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.20 2007/11/07 11:36:53 hal9 Exp $
+ $Id: p-config.sgml,v 2.29 2008/03/26 18:07:18 fabiankeil Exp $
- Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
See LICENSE.
========================================================================
@@ -95,10 +95,10 @@
Sample Configuration File for Privoxy v&p-version;
- $Id: p-config.sgml,v 2.20 2007/11/07 11:36:53 hal9 Exp $
+ $Id: p-config.sgml,v 2.29 2008/03/26 18:07:18 fabiankeil Exp $
-Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
+Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
@@ -354,7 +354,7 @@ II. FORMAT OF THE CONFIGURATION FILE
The value of this option only matters if the experimental trust mechanism has been
- activated. (See trustfile above.)
+ activated. (See trustfile below.)
If you use the trust mechanism, it is a good idea to write up some on-line
@@ -504,7 +504,7 @@ II. FORMAT OF THE CONFIGURATION FILE
Specifies:
- The directory where the other configuration files are located
+ The directory where the other configuration files are located.
@@ -529,7 +529,7 @@ II. FORMAT OF THE CONFIGURATION FILE
Notes:
- No trailing /, please
+ No trailing /, please.
The logfile is where all logging and error messages are written. The level
of detail and number of messages are set with the debug
@@ -850,15 +844,14 @@ actionsfile
is doing.
- Many users will never look at it, however, and it's a privacy risk
- if third parties can get access to it. It is therefore disabled by
- default in Privoxy 3.0.7 and later.
-
-
- For troubleshooting purposes, you will have to explicitly enable it.
- Please don't file any support requests without trying to reproduce
- the problem with logging enabled first. Once you read the log messages,
- you may even be able to solve the problem on your own.
+ Depending on the debug options below, the logfile may be a privacy risk
+ if third parties can get access to it. As most users will never look
+ at it, Privoxy 3.0.7 and later only log fatal
+ errors by default.
+
+
+ For most troubleshooting purposes, you will have to change that,
+ please refer to the debugging section for details.
Your logfile will grow indefinitely, and you will probably want to
@@ -866,19 +859,6 @@ actionsfile
(see man cron). For Red Hat based Linux distributions, a
logrotate script has been included.
-
Any log files must be writable by whatever user Privoxy
is being run as (on Unix, default user id is privoxy).
@@ -887,7 +867,7 @@ fk 2007-11-07
-@@#logfile logfile]]>
+@@logfile logfile]]>
@@ -912,7 +892,7 @@ fk 2007-11-07
Default value:
- Unset (commented out). When activated: jarfile (Unix) or privoxy.jar (Windows)
+ Unset (commented out). When activated: jarfile (Unix) or privoxy.jar (Windows).
@@ -1046,8 +1026,7 @@ fk 2007-11-07
Specifies:
- Key values that determine what information gets logged to the
- logfile.
+ Key values that determine what information gets logged.
@@ -1060,14 +1039,14 @@ fk 2007-11-07
Default value:
- 12289 (i.e.: URLs plus informational and warning messages)
+ 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)Effect if unset:
- Nothing gets logged.
+ Default value is used (see above).
@@ -1079,7 +1058,7 @@ fk 2007-11-07
- debug 1 # show each GET/POST/CONNECT request
+ debug 1 # log each request destination (and the crunch reason if &my-app; intercepted the request)
debug 2 # show each connection status
debug 4 # show I/O status
debug 8 # show header parsing
@@ -1089,7 +1068,7 @@ fk 2007-11-07
debug 128 # debug redirects
debug 256 # debug GIF de-animation
debug 512 # Common Log Format
- debug 1024 # debug kill pop-ups
+ debug 1024 # Unused
debug 2048 # CGI user interface
debug 4096 # Startup banner and warnings.
debug 8192 # Non-fatal errors
@@ -1101,18 +1080,23 @@ fk 2007-11-07
A debug level of 1 is informative because it will show you each request
- as it happens. 1, 4096 and 8192 are highly recommended
- so that you will notice when things go wrong. The other levels are probably
- only of interest if you are hunting down a specific problem. They can produce
- a hell of an output (especially 16).
+ as it happens. 1, 4096 and 8192 are recommended
+ so that you will notice when things go wrong. The other levels are
+ probably only of interest if you are hunting down a specific problem.
+ They can produce a hell of an output (especially 16).
- The reporting of fatal errors (i.e. ones which causes
- Privoxy to exit) is always on and cannot be disabled.
+ &my-app; used to ship with the debug levels recommended above enabled by
+ default, but due to privacy concerns 3.0.7 and later are configured to
+ only log fatal errors.
- If you want to use CLF (Common Log Format), you should set debug
+ If you are used to the more verbose settings, simply enable the debug lines
+ below again.
+
+
+ If you want to use pure CLF (Common Log Format), you should set debug
512ONLY and not enable anything else.
@@ -1120,13 +1104,18 @@ fk 2007-11-07
length of log messages. If it's reached, messages are logged truncated
and marked with ... [too long, truncated].
+
+ Please don't file any support requests without trying to reproduce
+ the problem with increased debug level first. Once you read the log
+ messages, you may even be able to solve the problem on your own.
+
-@@debug 1 # show each GET/POST/CONNECT request]]>
-@@debug 4096 # Startup banner and warnings]]>
-@@debug 8192 # Errors - *we highly recommended enabling this*]]>
+@@#debug 1 # log each request destination (and the crunch reason if &my-app; intercepted the request)]]>
+@@#debug 4096 # Startup banner and warnings]]>
+@@#debug 8192 # Non-fatal errors]]>
@@ -1138,7 +1127,7 @@ fk 2007-11-07
Specifies:
- Whether to run only one server thread
+ Whether to run only one server thread.
@@ -1167,8 +1156,8 @@ fk 2007-11-07
Notes:
- This option is only there for debugging purposes and you should never
- need to use it. It will drastically reduce performance.
+ This option is only there for debugging purposes.
+ It will drastically reduce performance.
@@ -1177,6 +1166,62 @@ fk 2007-11-07
@@#single-threaded]]>
+
+hostname
+
+
+
+ Specifies:
+
+
+ The hostname shown on the CGI pages.
+
+
+
+
+ Type of value:
+
+ Text
+
+
+
+ Default value:
+
+ Unset
+
+
+
+ Effect if unset:
+
+
+ The hostname provided by the operating system is used.
+
+
+
+
+ Notes:
+
+
+ On some misconfigured systems resolving the hostname fails or
+ takes too much time and slows Privoxy down. Setting a fixed hostname
+ works around the problem.
+
+
+ In other circumstances it might be desirable to show a hostname
+ other than the one returned by the operating system. For example
+ if the system has several different hostnames and you don't want
+ to use the first one.
+
+
+ Note that Privoxy does not validate the specified hostname value.
+
+
+
+
+
+@@#hostname hostname.example.org]]>
+
+
@@ -1390,7 +1435,7 @@ fk 2007-11-07
As a lot of Privoxy users don't read
- documentation, this feature has been disabled by default.
+ documentation, this feature is disabled by default.
Note that you must have compiled Privoxy with
@@ -1451,7 +1496,7 @@ fk 2007-11-07
side code (e.g Java) is also capable of using this feature.
- This option may be removed in future releases as it has been obsoleted
+ This option will be removed in future releases as it has been obsoleted
by the more general header taggers.
@@ -1506,7 +1551,8 @@ fk 2007-11-07
This option is not recommended for environments
- with untrusted users and is therefore disabled by default.
+ with untrusted users and as a lot of Privoxy
+ users don't read documentation, this feature is disabled by default.
Note that malicious client side code (e.g Java) is also
@@ -1514,10 +1560,6 @@ fk 2007-11-07
this options unless you understand the consequences and are
sure your browser is configured correctly.
-
- As a lot of Privoxy users don't read
- documentation, this feature has been disabled by default.
-
Note that you must have compiled Privoxy with
support for this feature, otherwise this option has no effect.
@@ -1663,9 +1705,9 @@ ACLs: permit-access and deny-access
option.
- Please see the warnings in the FAQ that this proxy is not intended to be a substitute
- for a firewall or to encourage anyone to defer addressing basic security
- weaknesses.
+ Please see the warnings in the FAQ that Privoxy
+ is not intended to be a substitute for a firewall or to encourage anyone
+ to defer addressing basic security weaknesses.
Multiple ACL lines are OK.
@@ -1899,8 +1941,8 @@ ACLs: permit-access and deny-access
- forward / caching-proxy.example-isp.net:8000
- forward .example-isp.net .
+ forward / caching-proxy.isp.example.net:8000
+ forward .isp.example.net .
@@ -1911,7 +1953,7 @@ ACLs: permit-access and deny-access
-forward-socks4 and forward-socks4a
+forward-socks4, forward-socks4a and forward-socks5
@@ -1933,13 +1975,16 @@ forward-socks4 and forward-socks4a
http_parent[:port]
- where target_pattern is a URL pattern
- that specifies to which requests (i.e. URLs) this forward rule shall apply. Use / to
- denote all URLs.
- http_parent and socks_proxy
- are IP addresses in dotted decimal notation or valid DNS names (http_parent
+ where target_pattern is a
+ URL pattern that specifies to which
+ requests (i.e. URLs) this forward rule shall apply. Use / to
+ denote all URLs. http_parent
+ and socks_proxy
+ are IP addresses in dotted decimal notation or valid DNS names
+ (http_parent
may be . to denote no HTTP forwarding), and the optional
- port parameters are TCP ports, i.e. integer values from 1 to 64535
+ port parameters are TCP ports,
+ i.e. integer values from 1 to 65535
@@ -1968,6 +2013,9 @@ forward-socks4 and forward-socks4a
is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
server, while in SOCKS 4 it happens locally.
+
+ With forward-socks5 the DNS resolution will happen on the remote server as well.
+
If http_parent is ., then requests are not
forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
@@ -1986,7 +2034,7 @@ forward-socks4 and forward-socks4a
- forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
+ forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
forward .example.com .
@@ -2000,8 +2048,8 @@ forward-socks4 and forward-socks4a
- To chain Privoxy and Tor, both running on the same system, you should use
- the rule:
+ To chain Privoxy and Tor, both running on the same system, you would use
+ something like:
@@ -2025,7 +2073,8 @@ forward-socks4 and forward-socks4a
Unencrypted connections to systems in these address ranges will
be as (un)secure as the local network is, but the alternative is that you
can't reach the local network through Privoxy
- at all.
+ at all. Of course this may actually be desired and there is no reason
+ to make these exceptions if you aren't sure you need them.
If you also want to be able to reach servers in your local network by
@@ -2055,8 +2104,8 @@ forward-socks4 and forward-socks4a
- Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
- isp-b.net. Both run Privoxy. Their forwarding
+ Assume that host-a has a PPP connection to isp-a.example.net. And host-b has a PPP connection to
+ isp-b.example.org. Both run Privoxy. Their forwarding
configuration can look like this:
@@ -2067,7 +2116,7 @@ forward-socks4 and forward-socks4a
forward / .
- forward .isp-b.net host-b:8118
+ forward .isp-b.example.net host-b:8118
@@ -2078,7 +2127,7 @@ forward-socks4 and forward-socks4a
forward / .
- forward .isp-a.net host-a:8118
+ forward .isp-a.example.org host-a:8118
@@ -2090,7 +2139,7 @@ forward-socks4 and forward-socks4a
If you intend to chain Privoxy and
- squid locally, then chain as
+ squid locally, then chaining as
browser -> squid -> privoxy is the recommended way.
@@ -2120,8 +2169,9 @@ forward-socks4 and forward-socks4a
- You could just as well decide to only forward requests for Windows executables through
- a virus-scanning parent proxy, say, on antivir.example.com, port 8010:
+ You could just as well decide to only forward requests you suspect
+ of leading to Windows executables through a virus-scanning parent proxy,
+ say, on antivir.example.com, port 8010:
@@ -2358,11 +2408,11 @@ forward-socks4 and forward-socks4a
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.
+ URL length limitations.
Enabling split-large-forms causes Privoxy
- to devide big forms into smaller ones to keep the URL length down.
+ to divide 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.
@@ -2594,7 +2644,7 @@ forward-socks4 and forward-socks4a
The hide-console option is specific to the MS-Win console
version of Privoxy. If this option is used,
- Privoxy will disconnect from and hide the
+ Privoxy will disconnect from and hide the
command console.