1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
6 <title>Contacting the Developers, Bug Reporting and Feature
8 <meta name="GENERATOR" content=
9 "Modular DocBook HTML Stylesheet Version 1.79">
10 <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
11 <link rel="PREVIOUS" title="Privoxy's Template Files" href=
13 <link rel="NEXT" title="Privoxy Copyright, License and History" href=
15 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
16 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
17 <link rel="STYLESHEET" type="text/css" href="p_doc.css">
20 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
21 "#840084" alink="#0000FF">
22 <div class="NAVHEADER">
23 <table summary="Header navigation table" width="100%" border="0"
24 cellpadding="0" cellspacing="0">
26 <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
30 <td width="10%" align="left" valign="bottom"><a href="templates.html"
31 accesskey="P">Prev</a></td>
33 <td width="80%" align="center" valign="bottom"></td>
35 <td width="10%" align="right" valign="bottom"><a href=
36 "copyright.html" accesskey="N">Next</a></td>
39 <hr align="left" width="100%">
43 <h1 class="SECT1"><a name="CONTACT" id="CONTACT">11. Contacting the
44 Developers, Bug Reporting and Feature Requests</a></h1>
46 <p>We value your feedback. In fact, we rely on it to improve <span class=
47 "APPLICATION">Privoxy</span> and its configuration. However, please note
48 the following hints, so we can provide you with the best support:</p>
51 <h2 class="SECT2"><a name="CONTACT-SUPPORT" id="CONTACT-SUPPORT">11.1.
54 <p>For casual users, our <a href=
55 "http://sourceforge.net/tracker/?group_id=11118&atid=211118"
56 target="_top">support forum at SourceForge</a> is probably best suited:
58 "http://sourceforge.net/tracker/?group_id=11118&atid=211118"
59 target="_top">http://sourceforge.net/tracker/?group_id=11118&atid=211118</a></p>
61 <p>All users are of course welcome to discuss their issues on the
62 <a href="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
63 target="_top">users mailing list</a>, where the developers also hang
66 <p>Please don't sent private support requests to individual Privoxy
67 developers, either use the mailing lists or the support trackers.</p>
69 <p>If you have to contact a Privoxy developer directly for other
70 reasons, please send a real mail and do not bother with SourceForge's
71 messaging system. Answers to SourceForge messages are usually bounced
72 by SourceForge's mail server in which case the developer wasted time
73 writing a response you don't get. From your point of view it will look
74 like your message has been completely ignored, so this is frustrating
75 for all parties involved.</p>
77 <p>Note that the Privoxy mailing lists are moderated. Posts from
78 unsubscribed addresses have to be accepted manually by a moderator.
79 This may cause a delay of several days and if you use a subject that
80 doesn't clearly mention Privoxy or one of its features, your message
81 may be accidentally discarded as spam.</p>
83 <p>If you aren't subscribed, you should therefore spend a few seconds
84 to come up with a proper subject. Additionally you should make it clear
85 that you want to get CC'd. Otherwise some responses will be directed to
86 the mailing list only, and you won't see them.</p>
90 <h2 class="SECT2"><a name="REPORTING" id="REPORTING">11.2. Reporting
93 <p><span class="QUOTE">"Problems"</span> for our purposes, come in two
98 <p>Configuration issues, such as ads that slip through, or sites
99 that don't function properly due to one <span class=
100 "APPLICATION">Privoxy</span> <span class="QUOTE">"action"</span> or
101 another being turned <span class="QUOTE">"on"</span>.</p>
105 <p><span class="QUOTE">"Bugs"</span> in the programming code that
106 makes up <span class="APPLICATION">Privoxy</span>, such as that
107 might cause a crash.</p>
112 <h3 class="SECT3"><a name="CONTACT-ADS" id="CONTACT-ADS">11.2.1.
113 Reporting Ads or Other Configuration Problems</a></h3>
115 <p>Please send feedback on ads that slipped through, innocent images
116 that were blocked, sites that don't work properly, and other
117 configuration related problem of <tt class=
118 "FILENAME">default.action</tt> file, to <a href=
119 "http://sourceforge.net/tracker/?group_id=11118&atid=460288"
121 "_top">http://sourceforge.net/tracker/?group_id=11118&atid=460288</a>,
122 the Actions File Tracker.</p>
124 <p>New, improved <tt class="FILENAME">default.action</tt> files may
125 occasionally be made available based on your feedback. These will be
126 announced on the <a href=
127 "http://lists.sourceforge.net/lists/listinfo/ijbswa-announce" target=
128 "_top">ijbswa-announce</a> list and available from our the <a href=
129 "http://sourceforge.net/project/showfiles.php?group_id=11118" target=
130 "_top">files section</a> of our <a href=
131 "http://sf.net/projects/ijbswa/" target="_top">project page</a>.</p>
135 <h3 class="SECT3"><a name="CONTACT-BUGS" id="CONTACT-BUGS">11.2.2.
136 Reporting Bugs</a></h3>
138 <p>Please report all bugs through our bug tracker: <a href=
139 "http://sourceforge.net/tracker/?group_id=11118&atid=111118"
141 "_top">http://sourceforge.net/tracker/?group_id=11118&atid=111118</a>.</p>
143 <p>Before doing so, please make sure that the bug has <span class=
144 "emphasis"><i class="EMPHASIS">not already been submitted</i></span>
145 and observe the additional hints at the top of the <a href=
146 "http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
147 target="_top">submit form</a>. If already submitted, please feel free
148 to add any info to the original report that might help to solve the
151 <p>Please try to verify that it is a <span class=
152 "APPLICATION">Privoxy</span> bug, and not a browser or site bug or
153 documented behaviour that just happens to be different than what you
154 expected. If unsure, try <a href=
155 "http://config.privoxy.org/toggle?set=disable" target="_top">toggling
156 off</a> <span class="APPLICATION">Privoxy</span>, and see if the
157 problem persists.</p>
159 <p>If you are using your own custom configuration, please try the
160 stock configs to see if the problem is configuration related. If
161 you're having problems with a feature that is disabled by default,
162 please ask around on the mailing list if others can reproduce the
165 <p>If you aren't using the latest Privoxy version, the bug may have
166 been found and fixed in the meantime. We would appreciate if you
167 could take the time to <a href=
168 "http://www.privoxy.org/user-manual/installation.html" target=
169 "_top">upgrade to the latest version</a> (or even the latest CVS
170 snapshot) and verify that your bug still exists.</p>
172 <p>Please be sure to provide the following information:</p>
176 <p>The exact <span class="APPLICATION">Privoxy</span> version you
177 are using (if you got the source from CVS, please also provide
178 the source code revisions as shown in <a href=
179 "http://config.privoxy.org/show-version" target=
180 "_top">http://config.privoxy.org/show-version</a>).</p>
184 <p>The operating system and versions you run <span class=
185 "APPLICATION">Privoxy</span> on, (e.g. <span class=
186 "APPLICATION">Windows XP SP2</span>), if you are using a Unix
187 flavor, sending the output of <span class="QUOTE">"uname
188 -a"</span> should do, in case of GNU/Linux, please also name the
193 <p>The name, platform, and version of the <span class=
194 "APPLICATION">browser</span> you were using (e.g. <span class=
195 "APPLICATION">Internet Explorer v5.5</span> for Mac).</p>
199 <p>The URL where the problem occurred, or some way for us to
200 duplicate the problem (e.g. <tt class=
201 "LITERAL">http://somesite.example.com/?somethingelse=123</tt>).</p>
205 <p>Whether your version of <span class=
206 "APPLICATION">Privoxy</span> is one supplied by the <span class=
207 "APPLICATION">Privoxy</span> developers via SourceForge, or if
208 you got your copy somewhere else.</p>
212 <p>Whether you are using <span class="APPLICATION">Privoxy</span>
213 in tandem with another proxy such as <span class=
214 "APPLICATION">Tor</span>. If so, please temporary disable the
215 other proxy to see if the symptoms change.</p>
219 <p>Whether you are using a personal firewall product. If so, does
220 <span class="APPLICATION">Privoxy</span> work without it?</p>
224 <p>Any other pertinent information to help identify the problem
225 such as config or log file excerpts (yes, you should have log
226 file entries for each action taken). To get a meaningful logfile,
227 please make sure that the <a href=
228 "../user-manual/config.html#LOGFILE" target="_top">logfile
229 directive</a> is being used and the following <a href=
230 "../user-manual/config.html#DEBUG" target="_top">debug
231 options</a> are enabled:</p>
233 <p class="LITERALLAYOUT">
234 debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
236 debug 2 # show each connection status<br>
238 debug 4 # show I/O status<br>
240 debug 8 # show header parsing<br>
242 debug 128 # debug redirects<br>
243 debug 256 # debug GIF de-animation<br>
245 debug 512 # Common Log Format<br>
247 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
249 debug 4096 # Startup banner and warnings.<br>
251 debug 8192 # Non-fatal errors</p>If you
252 are having trouble with a filter, please additionally enable
254 <p class="LITERALLAYOUT">
255 debug 64 # debug regular expression filters</p>If
256 you are using Privoxy 3.0.17 or later and suspect that it
257 interprets the request or the response incorrectly, please enable
259 <p class="LITERALLAYOUT">
260 debug 32768 # log all data read from the network</p>Note
261 that Privoxy log files may contain sensitive information so
262 please don't submit any logfiles you didn't read first. You can
263 mask sensitive information as long as it's clear that you removed
268 <p>You don't have to tell us your actual name when filing a problem
269 report, but if you don't, please use a nickname so we can
270 differentiate between your messages and the ones entered by other
271 "anonymous" users that may respond to your request if they have the
272 same problem or already found a solution. Note that due to spam the
273 trackers may not always allow to post without being logged into
274 SourceForge. If that's the case, you are still free to create a login
275 that isn't directly linked to your name, though.</p>
277 <p>Please also check the status of your request a few days after
278 submitting it, as we may request additional information. If you use a
279 SF id, you should automatically get a mail when someone responds to
280 your request. Please don't bother to add an email address when using
281 the tracker. If you prefer to communicate through email, just use one
282 of the mailing lists directly.</p>
284 <p>If you are new to reporting problems, you might be interested in
285 <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
286 target="_top">How to Report Bugs Effectively</a>.</p>
289 "http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
290 target="_top">appendix of the Privoxy User Manual</a> also has
291 helpful information on understanding <tt class=
292 "LITERAL">actions</tt>, and <tt class="LITERAL">action</tt>
298 <h2 class="SECT2"><a name="CONTACT-FEATURE" id="CONTACT-FEATURE">11.3.
299 Request New Features</a></h2>
301 <p>You are welcome to submit ideas on new features or other proposals
302 for improvement through our feature request tracker at <a href=
303 "http://sourceforge.net/tracker/?atid=361118&group_id=11118"
304 target="_top">http://sourceforge.net/tracker/?atid=361118&group_id=11118</a>.</p>
308 <h2 class="SECT2"><a name="MAILING-LISTS" id="MAILING-LISTS">11.4.
309 Mailing Lists</a></h2>
311 <p>If you prefer to communicate through email, instead of using a web
312 interface, feel free to use one of the mailing lists. To discuss issues
313 that haven't been completely diagnosed yet, please use the Privoxy
314 users list. Technically interested users and people who wish to
315 contribute to the project are always welcome on the developers list.
316 You can find an overview of all <span class=
317 "APPLICATION">Privoxy</span>-related mailing lists, including list
318 archives, at: <a href="http://sourceforge.net/mail/?group_id=11118"
319 target="_top">http://sourceforge.net/mail/?group_id=11118</a>.</p>
323 <div class="NAVFOOTER">
324 <hr align="left" width="100%">
326 <table summary="Footer navigation table" width="100%" border="0"
327 cellpadding="0" cellspacing="0">
329 <td width="33%" align="left" valign="top"><a href="templates.html"
330 accesskey="P">Prev</a></td>
332 <td width="34%" align="center" valign="top"><a href="index.html"
333 accesskey="H">Home</a></td>
335 <td width="33%" align="right" valign="top"><a href="copyright.html"
336 accesskey="N">Next</a></td>
340 <td width="33%" align="left" valign="top">Privoxy's Template
343 <td width="34%" align="center" valign="top"> </td>
345 <td width="33%" align="right" valign="top">Privoxy Copyright, License