X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=config;h=257ee19f9d9c52ea941765d6f89a0abf6daa63ff;hp=3c690a7205132645a0b3bbce6ff7f8ce19ccd362;hb=9087ae1aa5ec3738b8f7f473a04019e466b01dfc;hpb=cd2a0754809e4ef05ebf4230fe7e959385f16ec3 diff --git a/config b/config index 3c690a72..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: config,v 1.60 2007/12/08 14:30:40 hal9 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: # @@ -452,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 @@ -555,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: # @@ -564,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 @@ -617,9 +616,9 @@ filterfile default.filter # 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 1 # log each request destination (and the crunch reason if Privoxy intercepted the request) #debug 4096 # Startup banner and warnings -#debug 8192 # Errors - *we highly recommended enabling this* +#debug 8192 # Non-fatal errors # # # 3.2. single-threaded