+ action taken). To get a meaningful logfile, please make sure that the
+ <ulink url="../user-manual/config.html#LOGFILE">logfile directive</ulink>
+ is being used and the following <ulink
+ url="../user-manual/config.html#DEBUG">debug options</ulink> are enabled:
+ <literallayout>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 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 4096 # Startup banner and warnings.
+debug 8192 # Non-fatal errors</literallayout>
+ If you are having trouble with a filter, please additionally enable
+ <literallayout>debug 64 # debug regular expression filters</literallayout>
+ If you are using Privoxy 3.0.17 or later and suspect that it interprets the
+ request or the response incorrectly, please enable
+ <literallayout>debug 32768 # log all data read from the network</literallayout>
+ Note that Privoxy log files may contain sensitive information so please don't
+ submit any logfiles you didn't read first. You can mask sensitive information
+ as long as it's clear that you removed something.