+<para>
+ If you aren't using the latest Privoxy version, the problem may have been found
+ and fixed in the meantime. We would appreciate if you could take the time
+ to <ulink url="https://www.privoxy.org/user-manual/installation.html">upgrade
+ to the latest version</ulink> and verify that the problem still exists.
+</para>
+<para>
+ Please be sure to provide the following information when reporting problems
+ or requesting support:
+</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The exact <application>Privoxy</application> version you are using.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The operating system and versions you run
+ <application>Privoxy</application> on, e.g. <application>Windows
+ XP SP2</application>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The name, platform, and version of the <application>browser</application>
+ you were using (e.g. <application>Internet Explorer v5.5</application> for Mac).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The URL where the problem occurred, or some way for us to duplicate the
+ problem (e.g. <literal>http://somesite.example.com/?somethingelse=123</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Whether your version of <application>Privoxy</application> is one supplied
+ by the <application>Privoxy</application> developers via SourceForge,
+ or if you got your copy somewhere else.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Whether you are using <application>Privoxy</application> together with
+ another proxy such as <application>Tor</application>. If so, please
+ temporary disable the other proxy to see if the symptoms change.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Whether you are using a personal firewall product. If so, does
+ <application>Privoxy</application> work without it?
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ 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). 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
+ (all of them):
+ </para>
+ <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
+debug 65536 # Log applying actions</literallayout>
+ <para>
+ If you are having trouble with a filter, please additionally enable
+ </para>
+ <literallayout>debug 64 # debug regular expression filters</literallayout>
+ <para>
+ If you suspect that Privoxy interprets the request or the response
+ incorrectly, please enable
+ </para>
+ <literallayout>debug 32768 # log all data read from the network</literallayout>
+ <para>
+ It's easy for us to ignore log messages that aren't relevant but missing
+ log messages may make it impossible to investigate a problem. If you aren't
+ sure which of the debug directives are relevant, please just enable all of them
+ and let us worry about it.
+ </para>
+ <para>
+ 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.
+ </para>
+ </listitem>
+
+</itemizedlist>