X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=config;h=257ee19f9d9c52ea941765d6f89a0abf6daa63ff;hp=a7904995394fac8abf5a7a78a310017bbf85fde6;hb=5830cbd0c477214cec7f140023a7249a2d346b26;hpb=245fdf362f67d886babeeb5cca3fc719f69937e3

diff --git a/config b/config
index a7904995..257ee19f 100644
--- a/config
+++ b/config
@@ -1,8 +1,8 @@
-#        Sample Configuration File for Privoxy v3.0.7
+#        Sample Configuration File for Privoxy v3.0.8
 #
-#  $Id: p-config.sgml,v 2.22 2007/11/09 20:26:58 fabiankeil Exp $
+#  $Id: config,v 1.62 2007/12/09 07:51:46 fabiankeil Exp $
 #
-#  Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
+#  Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
 #
 ####################################################################
 #                                                                  #
@@ -426,7 +426,7 @@ filterfile default.filter
 #
 #  Effect if unset:
 #
-#      Logging is disabled unless --no-daemon mode is used.
+#      No logfile is written.
 #
 #  Notes:
 #
@@ -437,15 +437,12 @@ filterfile default.filter
 #      an ad you think it should block) and it can help you to monitor
 #      what your browser 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.
+#      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 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.
+#      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 periodically remove it. On Unix systems, you can do
@@ -455,7 +452,7 @@ filterfile default.filter
 #      Any log files must be writable by whatever user Privoxy is
 #      being run as (on Unix, default user id is "privoxy").
 #
-#logfile logfile
+logfile logfile
 #
 #
 #  2.7. jarfile
@@ -558,8 +555,7 @@ filterfile default.filter
 #
 #  Specifies:
 #
-#      Key values that determine what information gets logged to
-#      the logfile.
+#      Key values that determine what information gets logged.
 #
 #  Type of value:
 #
@@ -567,17 +563,17 @@ filterfile default.filter
 #
 #  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).
 #
 #  Notes:
 #
 #      The available debug levels are:
 #
-#        debug         1 # show each GET/POST/CONNECT request 
+#        debug         1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
 #        debug         2 # show each connection status 
 #        debug         4 # show I/O status 
 #        debug         8 # show header parsing 
@@ -597,21 +593,32 @@ filterfile default.filter
 #      use multiple debug lines.
 #
 #      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).
+#      request 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 512" ONLY and not enable anything else.
+#      Privoxy 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 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 512 ONLY and not enable anything else.
 #
 #      Privoxy has a hard-coded limit for the length of log messages. If
 #      it's reached, messages are logged truncated and marked with
 #      "... [too long, truncated]".
 #
-debug   1    # show each GET/POST/CONNECT request
-debug   4096 # Startup banner and warnings
-debug   8192 # Errors - *we highly recommended enabling this*
+#      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    # log each request destination (and the crunch reason if Privoxy intercepted the request)
+#debug   4096 # Startup banner and warnings
+#debug   8192 # Non-fatal errors
 #
 #
 #  3.2. single-threaded