1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
2 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 <meta name="generator" content="HTML Tidy, see www.w3.org">
7 Contacting the developers, Bug Reporting and Feature Requests
9 <meta name="GENERATOR" content=
10 "Modular DocBook HTML Stylesheet Version 1.79">
11 <link rel="HOME" title="Privoxy Frequently Asked Questions" href=
13 <link rel="PREVIOUS" title="Troubleshooting" href="trouble.html">
14 <link rel="NEXT" title="Privoxy Copyright, License and History" href=
16 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
17 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
18 <style type="text/css">
20 background-color: #EEEEEE;
23 :link { color: #0000FF }
24 :visited { color: #840084 }
25 :active { color: #0000FF }
26 hr.c1 {text-align: left}
30 <div class="NAVHEADER">
31 <table summary="Header navigation table" width="100%" border="0"
32 cellpadding="0" cellspacing="0">
34 <th colspan="3" align="center">
35 Privoxy Frequently Asked Questions
39 <td width="10%" align="left" valign="bottom">
40 <a href="trouble.html" accesskey="P">Prev</a>
42 <td width="80%" align="center" valign="bottom">
44 <td width="10%" align="right" valign="bottom">
45 <a href="copyright.html" accesskey="N">Next</a>
49 <hr width="100%" class="c1">
53 <a name="CONTACT">6. Contacting the developers, Bug Reporting and
57 We value your feedback. In fact, we rely on it to improve <span
58 class="APPLICATION">Privoxy</span> and its configuration. However,
59 please note the following hints, so we can provide you with the best
64 <a name="CONTACT-SUPPORT">6.1. Get Support</a>
67 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
71 "http://sourceforge.net/tracker/?group_id=11118&atid=211118"
73 "_top">http://sourceforge.net/tracker/?group_id=11118&atid=211118</a>
76 All users are of course welcome to discuss their issues on the <a
77 href="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
78 target="_top">users mailing list</a>, where the developers also
82 Please don't sent private support requests to individual Privoxy
83 developers, either use the mailing lists or the support trackers.
86 If you have to contact a Privoxy developer directly for other
87 reasons, please send a real mail and do not bother with
88 SourceForge's messaging system. Answers to SourceForge messages are
89 usually bounced by SourceForge's mail server in which case the
90 developer wasted time writing a response you don't get. From your
91 point of view it will look like your message has been completely
92 ignored, so this is frustrating for all parties involved.
95 Note that the Privoxy mailing lists are moderated. Posts from
96 unsubscribed addresses have to be accepted manually by a moderator.
97 This may cause a delay of several days and if you use a subject
98 that doesn't clearly mention Privoxy or one of its features, your
99 message may be accidentally discarded as spam.
102 If you aren't subscribed, you should therefore spend a few seconds
103 to come up with a proper subject. Additionally you should make it
104 clear that you want to get CC'd. Otherwise some responses will be
105 directed to the mailing list only, and you won't see them.
110 <a name="REPORTING">6.2. Reporting Problems</a>
113 <span class="QUOTE">"Problems"</span> for our purposes, come in two
119 Configuration issues, such as ads that slip through, or sites
120 that don't function properly due to one <span class=
121 "APPLICATION">Privoxy</span> <span class=
122 "QUOTE">"action"</span> or another being turned <span class=
128 <span class="QUOTE">"Bugs"</span> in the programming code that
129 makes up <span class="APPLICATION">Privoxy</span>, such as that
136 <a name="CONTACT-ADS">6.2.1. Reporting Ads or Other Configuration
140 Please send feedback on ads that slipped through, innocent images
141 that were blocked, sites that don't work properly, and other
142 configuration related problem of <tt class=
143 "FILENAME">default.action</tt> file, to <a href=
144 "http://sourceforge.net/tracker/?group_id=11118&atid=460288"
146 "_top">http://sourceforge.net/tracker/?group_id=11118&atid=460288</a>,
147 the Actions File Tracker.
150 New, improved <tt class="FILENAME">default.action</tt> files may
151 occasionally be made available based on your feedback. These will
152 be announced on the <a href=
153 "http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
154 target="_top">ijbswa-announce</a> list and available from our the
156 "http://sourceforge.net/project/showfiles.php?group_id=11118"
157 target="_top">files section</a> of our <a href=
158 "http://sf.net/projects/ijbswa/" target="_top">project page</a>.
163 <a name="CONTACT-BUGS">6.2.2. Reporting Bugs</a>
166 Please report all bugs through our bug tracker: <a href=
167 "http://sourceforge.net/tracker/?group_id=11118&atid=111118"
169 "_top">http://sourceforge.net/tracker/?group_id=11118&atid=111118</a>.
172 Before doing so, please make sure that the bug has <span class=
173 "emphasis"><i class="EMPHASIS">not already been
174 submitted</i></span> and observe the additional hints at the top
176 "http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
177 target="_top">submit form</a>. If already submitted, please feel
178 free to add any info to the original report that might help to
182 Please try to verify that it is a <span class=
183 "APPLICATION">Privoxy</span> bug, and not a browser or site bug
184 or documented behaviour that just happens to be different than
185 what you expected. If unsure, try <a href=
186 "http://config.privoxy.org/toggle?set=disable" target=
187 "_top">toggling off</a> <span class="APPLICATION">Privoxy</span>,
188 and see if the problem persists.
191 If you are using your own custom configuration, please try the
192 stock configs to see if the problem is configuration related. If
193 you're having problems with a feature that is disabled by
194 default, please ask around on the mailing list if others can
195 reproduce the problem.
198 If you aren't using the latest Privoxy version, the bug may have
199 been found and fixed in the meantime. We would appreciate if you
200 could take the time to <a href=
201 "http://www.privoxy.org/user-manual/installation.html" target=
202 "_top">upgrade to the latest version</a> (or even the latest CVS
203 snapshot) and verify that your bug still exists.
206 Please be sure to provide the following information:
213 The exact <span class="APPLICATION">Privoxy</span> version
214 you are using (if you got the source from CVS, please also
215 provide the source code revisions as shown in <a href=
216 "http://config.privoxy.org/show-version" target=
217 "_top">http://config.privoxy.org/show-version</a>).
222 The operating system and versions you run <span class=
223 "APPLICATION">Privoxy</span> on, (e.g. <span class=
224 "APPLICATION">Windows XP SP2</span>), if you are using a Unix
225 flavor, sending the output of <span class="QUOTE">"uname
226 -a"</span> should do, in case of GNU/Linux, please also name
232 The name, platform, and version of the <span class=
233 "APPLICATION">browser</span> you were using (e.g. <span
234 class="APPLICATION">Internet Explorer v5.5</span> for Mac).
239 The URL where the problem occurred, or some way for us to
240 duplicate the problem (e.g. <tt class=
241 "LITERAL">http://somesite.example.com/?somethingelse=123</tt>).
246 Whether your version of <span class=
247 "APPLICATION">Privoxy</span> is one supplied by the <span
248 class="APPLICATION">Privoxy</span> developers via
249 SourceForge, or if you got your copy somewhere else.
254 Whether you are using <span class=
255 "APPLICATION">Privoxy</span> in tandem with another proxy
256 such as <span class="APPLICATION">Tor</span>. If so, please
257 temporary disable the other proxy to see if the symptoms
263 Whether you are using a personal firewall product. If so,
264 does <span class="APPLICATION">Privoxy</span> work without
270 Any other pertinent information to help identify the problem
271 such as config or log file excerpts (yes, you should have log
272 file entries for each action taken). To get a meaningful
273 logfile, please make sure that the <a href=
274 "../user-manual/config.html#LOGFILE" target="_top">logfile
275 directive</a> is being used and the following <a href=
276 "../user-manual/config.html#DEBUG" target="_top">debug
277 options</a> are enabled:
279 <p class="LITERALLAYOUT">
280 debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
282 debug 2 # show each connection status<br>
284 debug 4 # show I/O status<br>
286 debug 8 # show header parsing<br>
288 debug 128 # debug redirects<br>
290 debug 256 # debug GIF de-animation<br>
292 debug 512 # Common Log Format<br>
294 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
296 debug 4096 # Startup banner and warnings.<br>
298 debug 8192 # Non-fatal errors
300 If you are having trouble with a filter, please additionally
302 <p class="LITERALLAYOUT">
303 debug 64 # debug regular expression filters
305 If you are using Privoxy 3.0.17 or later and suspect that it
306 interprets the request or the response incorrectly, please
308 <p class="LITERALLAYOUT">
309 debug 32768 # log all data read from the network
311 Note that Privoxy log files may contain sensitive information
312 so please don't submit any logfiles you didn't read first. You
313 can mask sensitive information as long as it's clear that you
314 removed something.<br>
319 You don't have to tell us your actual name when filing a problem
320 report, but if you don't, please use a nickname so we can
321 differentiate between your messages and the ones entered by other
322 "anonymous" users that may respond to your request if they have
323 the same problem or already found a solution. Note that due to
324 spam the trackers may not always allow to post without being
325 logged into SourceForge. If that's the case, you are still free
326 to create a login that isn't directly linked to your name,
330 Please also check the status of your request a few days after
331 submitting it, as we may request additional information. If you
332 use a SF id, you should automatically get a mail when someone
333 responds to your request. Please don't bother to add an email
334 address when using the tracker. If you prefer to communicate
335 through email, just use one of the mailing lists directly.
339 "http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
340 target="_top">appendix of the Privoxy User Manual</a> also has
341 helpful information on understanding <tt class=
342 "LITERAL">actions</tt>, and <tt class="LITERAL">action</tt>
349 <a name="CONTACT-FEATURE">6.3. Request New Features</a>
352 You are welcome to submit ideas on new features or other proposals
353 for improvement through our feature request tracker at <a href=
354 "http://sourceforge.net/tracker/?atid=361118&group_id=11118"
356 "_top">http://sourceforge.net/tracker/?atid=361118&group_id=11118</a>.
361 <a name="MAILING-LISTS">6.4. Mailing Lists</a>
364 If you prefer to communicate through email, instead of using a web
365 interface, feel free to use one of the mailing lists. To discuss
366 issues that haven't been completely diagnosed yet, please use the
367 Privoxy users list. Technically interested users and people who
368 wish to contribute to the project are always welcome on the
369 developers list. You can find an overview of all <span class=
370 "APPLICATION">Privoxy</span>-related mailing lists, including list
371 archives, at: <a href="http://sourceforge.net/mail/?group_id=11118"
372 target="_top">http://sourceforge.net/mail/?group_id=11118</a>.
376 <div class="NAVFOOTER">
377 <hr width="100%" class="c1">
378 <table summary="Footer navigation table" width="100%" border="0"
379 cellpadding="0" cellspacing="0">
381 <td width="33%" align="left" valign="top">
382 <a href="trouble.html" accesskey="P">Prev</a>
384 <td width="34%" align="center" valign="top">
385 <a href="index.html" accesskey="H">Home</a>
387 <td width="33%" align="right" valign="top">
388 <a href="copyright.html" accesskey="N">Next</a>
392 <td width="33%" align="left" valign="top">
395 <td width="34%" align="center" valign="top">
398 <td width="33%" align="right" valign="top">
399 Privoxy Copyright, License and History