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