X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=2eba9a1b04cb604f453c1955c43a594793543eee;hb=c54228f0ef0172341cfe4f9acb7e955fa1e269b7;hp=8cef79706cb6b1e6c46c2b59ebd412eef2ad1195;hpb=8855a031e62cf14ac96b06e773f8bad01d3a4e25;p=privoxy.git
diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index 8cef7970..2eba9a1b 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.21 2007/11/07 18:50:39 fabiankeil Exp $
+ $Id: p-config.sgml,v 2.26 2007/12/16 15:49:24 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.21 2007/11/07 18:50:39 fabiankeil Exp $
+ $Id: p-config.sgml,v 2.26 2007/12/16 15:49:24 fabiankeil Exp $
-Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
+Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
@@ -828,20 +828,13 @@ actionsfile
Effect if unset:
- Logging is disabled unless --no-daemon mode is used.
+ No logfile is written.
Notes:
-
The logfile is where all logging and error messages are written. The level
of detail and number of messages are set with the debug
@@ -851,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
@@ -867,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).
@@ -888,7 +867,7 @@ fk 2007-11-07
-@@#logfile logfile]]>
+@@logfile logfile]]>
@@ -1047,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.
@@ -1061,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).
@@ -1080,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
@@ -1102,24 +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).
-
- If you want to use CLF (Common Log Format), you should set debug
+ If you want to use pure CLF (Common Log Format), you should set debug
512ONLY and not enable anything else.
@@ -1127,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]]>
@@ -1516,7 +1498,6 @@ fk 2007-11-07
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
capable of using the actions editor and you shouldn't enable
@@ -2365,11 +2346,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.