ajoergensen/privoxy repository overview

 The available debug levels are:

   debug     1 # Log the destination for each request Privoxy let through. See also debug 1024.
   debug     2 # show each connection status
   debug     4 # show I/O status
   debug     8 # show header parsing
   debug    16 # log all data written to the network
   debug    32 # debug force feature
   debug    64 # debug regular expression filters
   debug   128 # debug redirects
   debug   256 # debug GIF de-animation
   debug   512 # Common Log Format
   debug  1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
   debug  2048 # CGI user interface
   debug  4096 # Startup banner and warnings.
   debug  8192 # Non-fatal errors
   debug 32768 # log all data read from the network
   debug 65536 # Log the applying actions

 To select multiple debug levels, you can either add them or
 use multiple debug lines.

 A debug level of 1 is informative because it will show you
 each request as it happens. 1, 1024, 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 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]".

 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.

Copy