<!--
- File : $Source: /cvsroot/ijbswa/current/doc/source/contacting.sgml,v $
+ File : doc/source/contacting.sgml
Purpose : Entity included in other project documents.
- $Id: contacting.sgml,v 2.40 2014/12/19 12:29:53 fabiankeil Exp $
-
- Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
See LICENSE.
======================================================================
<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="http://www.privoxy.org/user-manual/installation.html">upgrade
+ 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>
-<para>
<itemizedlist>
<listitem>
is being used and the following <ulink
url="../user-manual/config.html#DEBUG">debug options</ulink> are enabled
(all of them):
- <literallayout>debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
+ </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 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>
- </para>
+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>
- 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>
+ <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
</listitem>
</itemizedlist>
-</para>
<para>
You don't have to tell us your actual name when filing a problem
<para>
If you are new to reporting problems, you might be interested in
- <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
+ <ulink url="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
>How to Report Bugs Effectively</ulink>.
</para>
<para>
- The <ulink url="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT">appendix
+ The <ulink url="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT">appendix
of the Privoxy User Manual</ulink> also has helpful information
on understanding <literal>actions</literal>, and <literal>action</literal> debugging.
</para>
<sect2 id="contact-support"><title>Get Support</title>
<para>
All users are welcome to discuss their issues on the <ulink
- url="http://lists.sourceforge.net/lists/listinfo/ijbswa-users">users
+ url="https://lists.privoxy.org/mailman/listinfo/privoxy-users">users
mailing list</ulink>, where the developers also hang around.
</para>
Please send feedback on ads that slipped through, innocent images that were
blocked, sites that don't work properly, and other configuration related problem of
<filename>default.action</filename> file, to
- <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=460288">
- http://sourceforge.net/tracker/?group_id=11118&atid=460288</ulink>,
+ <ulink url="https://sourceforge.net/p/ijbswa/actionsfile-feedback/"
+ >https://sourceforge.net/p/ijbswa/actionsfile-feedback/</ulink>,
the Actions File Tracker.
</para>
<para>
Before reporting bugs, please make sure that the bug has <emphasis>not already been submitted</emphasis>
and observe the additional hints at the top of the <ulink
- url="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118">submit
+ url="https://sourceforge.net/p/ijbswa/bugs/">submit
form</ulink>. If already submitted, please feel free to add any info to the
original report that might help to solve the issue.
</para>
the project are always welcome on the developers list.
You can find an overview of all <application>Privoxy</application>-related mailing lists,
including list archives, at:
-<ulink url="http://sourceforge.net/mail/?group_id=11118">http://sourceforge.net/mail/?group_id=11118</ulink>.
+<ulink url="https://lists.privoxy.org/mailman/listinfo">https://lists.privoxy.org/mailman/listinfo</ulink>.
+The lists hosted on privoxy.org have been created in 2016, the previously-used
+lists hosted at SourceForge are deprecated but the archives may still be useful:
+<ulink url="https://sourceforge.net/p/ijbswa/mailman/">https://sourceforge.net/p/ijbswa/mailman/</ulink>.
</para>
</sect2>
<sect2 id="sf-trackers"><title>SourceForge support trackers</title>
<para>
The
- <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">SourceForge support trackers</ulink>
+ <ulink url="https://sourceforge.net/p/ijbswa/support-requests/">SourceForge support trackers</ulink>
may be used as well, but have various technical problems that are unlikely to
be fixed anytime soon. If you don't get a timely response, please try the
- mailing list as well. While it's hosted at SourceForge as well, it usually
- works as expected.
+ mailing list as well.
</para>
</sect2>
projects / privoxy.git / blobdiff