<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Contacting the Developers, Bug Reporting and Feature
Requests</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Privoxy 3.0.32 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy's Template Files"
HREF="templates.html"><LINK
REL="NEXT"
TITLE="Privoxy Copyright, License and History"
HREF="copyright.html"><LINK
REL="STYLESHEET"
TYPE="text/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
CLASS="SECT1"
BGCOLOR="#EEEEEE"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Privoxy 3.0.32 User Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="CONTACT"
>11. Contacting the Developers, Bug Reporting and Feature
Requests</A
></H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> and its configuration.
However, please note the following hints, so we can
provide you with the best support.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="SUFFICIENT-INFORMATION"
>11.1. Please provide sufficient information</A
></H2
><P
> A lot of support requests don't contain enough information and can't
be solved without a lot of back and forth which causes unnecessary
delays. Reading this section should help to prevent that.</P
><P
> Before contacting us to report a problem, please try to verify that it is a
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> problem, and not a browser or site problem
or documented behaviour that just happens to be different than what you expected.
If unsure,
try <A
HREF="http://config.privoxy.org/toggle?set=disable"
TARGET="_top"
>toggling
off</A
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, and see if the problem persists.</P
><P
> If you are using your own custom configuration, please try the default
configuration to see if the problem is configuration related.
If you're having problems with a feature that is disabled by default,
please ask around on the mailing list if others can reproduce the problem.</P
><P
> 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 <A
HREF="https://www.privoxy.org/user-manual/installation.html"
TARGET="_top"
>upgrade
to the latest version</A
> and verify that the problem still exists.</P
><P
> Please be sure to provide the following information when reporting problems
or requesting support:</P
><P
></P
><UL
><LI
><P
> The exact <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> version you are using.
</P
></LI
><LI
><P
> The operating system and versions you run
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> on, e.g. <SPAN
CLASS="APPLICATION"
>Windows
XP SP2</SPAN
>.
</P
></LI
><LI
><P
> The name, platform, and version of the <SPAN
CLASS="APPLICATION"
>browser</SPAN
>
you were using (e.g. <SPAN
CLASS="APPLICATION"
>Internet Explorer v5.5</SPAN
> for Mac).
</P
></LI
><LI
><P
> The URL where the problem occurred, or some way for us to duplicate the
problem (e.g. <TT
CLASS="LITERAL"
>http://somesite.example.com/?somethingelse=123</TT
>).
</P
></LI
><LI
><P
> Whether your version of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> is one supplied
by the <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> developers,
or if you got your copy somewhere else.
</P
></LI
><LI
><P
> Whether you are using <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> together with
another proxy such as <SPAN
CLASS="APPLICATION"
>Tor</SPAN
>. If so, please
temporary disable the other proxy to see if the symptoms change.
</P
></LI
><LI
><P
> Whether you are using a personal firewall product. If so, does
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> work without it?
</P
></LI
><LI
><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). 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
(all of them):
</P
><P
CLASS="LITERALLAYOUT"
>debug 1 # Log the destination for each request Privoxy let through.<br>
# See also debug 1024.<br>
debug 2 # show each connection status<br>
debug 4 # show tagging-related messages<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,<br>
# and the reason why.<br>
debug 4096 # Startup banner and warnings.<br>
debug 8192 # Non-fatal errors<br>
debug 65536 # Log applying actions</P
><P
> If you are having trouble with a filter, please additionally enable
</P
><P
CLASS="LITERALLAYOUT"
>debug 64 # debug regular expression filters</P
><P
> If you suspect that Privoxy interprets the request or the response
incorrectly, please enable additionally
</P
><P
CLASS="LITERALLAYOUT"
>debug 32768 # log all data read from the network</P
><P
> 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.
</P
><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
><P
> You don't have to tell us your actual name when filing a problem
report, but if you don't, please use a nickname so we can differentiate
between your messages and the ones entered by other "anonymous" users that
may respond to your request if they have the same problem or already
found a solution. Note that due to spam the trackers may not always
allow to post without being logged into SourceForge. If that's the
case, you are still free to create a login that isn't directly linked
to your name, though.</P
><P
> Please also check the status of your request a few days after submitting
it, as we may request additional information. If you use a SF id,
you should automatically get a mail when someone responds to your request.
Please don't bother to add an email address when using the tracker.
If you prefer to communicate through email, just use one of the mailing
lists directly.</P
><P
> The <A
HREF="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
TARGET="_top"
>appendix
of the Privoxy User Manual</A
> also has helpful information
on understanding <TT
CLASS="LITERAL"
>actions</TT
>, and <TT
CLASS="LITERAL"
>action</TT
> debugging.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="CONTACT-SUPPORT"
>11.2. Get Support</A
></H2
><P
> All users are welcome to discuss their issues on the <A
HREF="https://lists.privoxy.org/mailman/listinfo/privoxy-users"
TARGET="_top"
>users
mailing list</A
>, where the developers also hang around.</P
><P
> Please don't send private support requests to individual Privoxy
developers, either use the mailing lists or the support trackers.</P
><P
> If you have to contact a Privoxy developer directly for other reasons,
please send a real mail and do not bother with SourceForge's messaging
system. Answers to SourceForge messages are usually bounced by SourceForge's
mail server in which case the developer wasted time writing a response you
don't get. From your point of view it will look like your message has
been completely ignored, so this is frustrating for all parties involved.</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
mention Privoxy or one of its features, your message may be accidentally
discarded as spam.</P
><P
> If you aren't subscribed, you should therefore spend a few seconds
to come up with a proper subject. Additionally you should make it clear
that you want to get CC'd. Otherwise some responses will be directed to
the mailing list only, and you won't see them.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="REPORTING"
>11.3. Reporting Problems</A
></H2
><P
><SPAN
CLASS="QUOTE"
>"Problems"</SPAN
> for our purposes, come in two forms:</P
><P
></P
><UL
><LI
><P
> Configuration issues, such as ads that slip through, or sites that
don't function properly due to one <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
<SPAN
CLASS="QUOTE"
>"action"</SPAN
> or another being turned <SPAN
CLASS="QUOTE"
>"on"</SPAN
>.
</P
></LI
><LI
><P
> <SPAN
CLASS="QUOTE"
>"Bugs"</SPAN
> in the programming code that makes up
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, such as that might cause a crash.
Documentation issues, for example spelling errors and unclear descriptions,
are bugs, too.
</P
></LI
></UL
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="CONTACT-ADS"
>11.3.1. Reporting Ads or Other Configuration Problems</A
></H3
><P
> 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
<TT
CLASS="FILENAME"
>default.action</TT
> file, to
<A
HREF="https://sourceforge.net/p/ijbswa/actionsfile-feedback/"
TARGET="_top"
>https://sourceforge.net/p/ijbswa/actionsfile-feedback/</A
>,
the Actions File Tracker.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="CONTACT-BUGS"
>11.3.2. Reporting Bugs</A
></H3
><P
> Before reporting bugs, please make sure that the bug has <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>not already been submitted</I
></SPAN
>
and observe the additional hints at the top of the <A
HREF="https://sourceforge.net/p/ijbswa/bugs/"
TARGET="_top"
>submit
form</A
>. If already submitted, please feel free to add any info to the
original report that might help to solve the issue.</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="SECURITY-CONTACT"
>11.4. Reporting security problems</A
></H2
><P
> If you discovered a security problem or merely suspect that a bug might
be a security issue, please mail Fabian Keil <fk@fabiankeil.de>
(OpenPGP fingerprint: 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C).</P
><P
> Usually you should get a response within a day, otherwise it's
likely that either your mail or the response didn't make it.
If that happens, please mail to the developer list to request a
status update.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="MAILING-LISTS"
>11.5. Mailing Lists</A
></H2
><P
>If you prefer to communicate through email, instead of using a web interface,
feel free to use one of the mailing lists.
To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
users list. Technically interested users and people who wish to contribute to
the project are always welcome on the developers list.
You can find an overview of all <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>-related mailing lists,
including list archives, at:
<A
HREF="https://lists.privoxy.org/mailman/listinfo"
TARGET="_top"
>https://lists.privoxy.org/mailman/listinfo</A
>.
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:
<A
HREF="https://sourceforge.net/p/ijbswa/mailman/"
TARGET="_top"
>https://sourceforge.net/p/ijbswa/mailman/</A
>.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="SF-TRACKERS"
>11.6. SourceForge support trackers</A
></H2
><P
> The
<A
HREF="https://sourceforge.net/p/ijbswa/support-requests/"
TARGET="_top"
>SourceForge support trackers</A
>
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.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Privoxy's Template Files</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Privoxy Copyright, License and History</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
distrib
>
Mageia
>
7
>
armv7hl
>
media
>
core-updates
>
by-pkgid
>
caead09f71a057684f628a1f930dd384
>
files
>
121
