NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.7 User Manual"
+TITLE="Privoxy 3.0.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy's Template Files"
HREF="copyright.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css">
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1">
<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
</head
><BODY
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.7 User Manual</TH
+>Privoxy 3.0.16 User Manual</TH
></TR
><TR
><TD
><P
> For casual users, our
<A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
+HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
TARGET="_top"
>support forum at SourceForge</A
>
is probably best suited:
<A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
+HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
TARGET="_top"
>http://sourceforge.net/tracker/?group_id=11118&atid=211118</A
></P
mailing list</A
>, where the developers also hang around.</P
><P
+> Please don't sent private support requests to individual Privoxy
+ developers, either use the mailing lists or the support trackers.</P
+><P
> Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
addresses have to be accepted manually by a moderator. This may cause a
delay of several days and if you use a subject that doesn't clearly
>default.action</TT
> file, to
<A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
+HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
TARGET="_top"
> http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
>,
><P
> Please report all bugs through our bug tracker:
<A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
+HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
TARGET="_top"
>http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
>. </P
></SPAN
>
and observe the additional hints at the top of the <A
-HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
+HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
TARGET="_top"
>submit
form</A
><P
> Any other pertinent information to help identify the problem such as config
or log file excerpts (yes, you should have log file entries for each
- action taken).
+ action taken). To get a meaningful logfile, please make sure that the
+ <A
+HREF="../user-manual/config.html#LOGFILE"
+TARGET="_top"
+>logfile directive</A
+>
+ is being used and the following <A
+HREF="../user-manual/config.html#DEBUG"
+TARGET="_top"
+>debug options</A
+> are enabled:
+ <P
+CLASS="LITERALLAYOUT"
+>debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
+debug 2 # show each connection status<br>
+debug 4 # show I/O status<br>
+debug 8 # show header parsing<br>
+debug 128 # debug redirects<br>
+debug 256 # debug GIF de-animation<br>
+debug 512 # Common Log Format<br>
+debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
+debug 4096 # Startup banner and warnings.<br>
+debug 8192 # Non-fatal errors</P
+>
+ If you are having trouble with a filter, please additionally enable
+ <P
+CLASS="LITERALLAYOUT"
+>debug 64 # debug regular expression filters</P
+>
+ 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.
</P
></LI
></UL
> You are welcome to submit ideas on new features or other proposals
for improvement through our feature request tracker at
<A
-HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
+HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
TARGET="_top"
>http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
>.</P