1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Contacting the developers, Bug Reporting and Feature Requests</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy Developer Manual"
11 HREF="index.html"><LINK
13 TITLE="Update the Webserver"
14 HREF="webserver-update.html"><LINK
16 TITLE="Privoxy Copyright, License and History"
17 HREF="copyright.html"><LINK
20 HREF="../p_doc.css"><META
21 HTTP-EQUIV="Content-Type"
23 charset=ISO-8859-1"></HEAD
34 SUMMARY="Header navigation table"
43 >Privoxy Developer Manual</TH
51 HREF="webserver-update.html"
80 >8. Contacting the developers, Bug Reporting and Feature Requests</A
83 > We value your feedback. In fact, we rely on it to improve
87 > and its configuration.
88 However, please note the following hints, so we can
89 provide you with the best support:</P
95 NAME="CONTACT-SUPPORT"
99 > For casual users, our
101 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
103 >support forum at SourceForge</A
105 is probably best suited:
107 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
109 >http://sourceforge.net/tracker/?group_id=11118&atid=211118</A
112 > All users are of course welcome to discuss their issues on the <A
113 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
117 >, where the developers also hang around.</P
119 > Please don't sent private support requests to individual Privoxy
120 developers, either use the mailing lists or the support trackers.</P
122 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
123 addresses have to be accepted manually by a moderator. This may cause a
124 delay of several days and if you use a subject that doesn't clearly
125 mention Privoxy or one of its features, your message may be accidentally
126 discarded as spam.</P
128 > If you aren't subscribed, you should therefore spend a few seconds
129 to come up with a proper subject. Additionally you should make it clear
130 that you want to get CC'd. Otherwise some responses will be directed to
131 the mailing list only, and you won't see them.</P
139 >8.2. Reporting Problems</A
145 > for our purposes, come in two forms:</P
151 > Configuration issues, such as ads that slip through, or sites that
152 don't function properly due to one <SPAN
159 > or another being turned <SPAN
170 > in the programming code that makes up
174 >, such as that might cause a crash.
184 >8.2.1. Reporting Ads or Other Configuration Problems</A
187 > Please send feedback on ads that slipped through, innocent images that were
188 blocked, sites that don't work properly, and other configuration related problem of
194 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
196 > http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
198 the Actions File Tracker.</P
203 > files may occasionally be made
204 available based on your feedback. These will be announced on the <A
205 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
209 list and available from our the <A
210 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
215 HREF="http://sf.net/projects/ijbswa/"
226 >8.2.2. Reporting Bugs</A
229 > Please report all bugs through our bug tracker:
231 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
233 >http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
236 > Before doing so, please make sure that the bug has <SPAN
240 >not already been submitted</I
243 and observe the additional hints at the top of the <A
244 HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
248 >. If already submitted, please feel free to add any info to the
249 original report that might help to solve the issue.</P
251 > Please try to verify that it is a <SPAN
255 and not a browser or site bug or documented behaviour that just happens
256 to be different than what you expected. If unsure,
258 HREF="http://config.privoxy.org/toggle?set=disable"
265 >, and see if the problem persists.</P
267 > If you are using your own custom configuration, please try
268 the stock configs to see if the problem is configuration related.
269 If you're having problems with a feature that is disabled by default,
270 please ask around on the mailing list if others can reproduce the problem.</P
272 > If you aren't using the latest Privoxy version, the bug may have been found
273 and fixed in the meantime. We would appreciate if you could take the time
275 HREF="http://www.privoxy.org/user-manual/installation.html"
278 to the latest version</A
279 > (or even the latest CVS snapshot) and verify
280 that your bug still exists.</P
282 >Please be sure to provide the following information:</P
292 > version you are using
293 (if you got the source from CVS, please also provide the source code revisions
295 HREF="http://config.privoxy.org/show-version"
297 >http://config.privoxy.org/show-version</A
303 > The operating system and versions you run
311 >), if you are using a Unix flavor,
312 sending the output of <SPAN
316 in case of GNU/Linux, please also name the distribution.
321 > The name, platform, and version of the <SPAN
325 you were using (e.g. <SPAN
327 >Internet Explorer v5.5</SPAN
333 > The URL where the problem occurred, or some way for us to duplicate the
336 >http://somesite.example.com/?somethingelse=123</TT
342 > Whether your version of <SPAN
349 > developers via SourceForge,
350 or if you got your copy somewhere else.
355 > Whether you are using <SPAN
359 another proxy such as <SPAN
363 temporary disable the other proxy to see if the symptoms change.
368 > Whether you are using a personal firewall product. If so, does
377 > Any other pertinent information to help identify the problem such as config
378 or log file excerpts (yes, you should have log file entries for each
379 action taken). To get a meaningful logfile, please make sure that the
381 HREF="../user-manual/config.html#LOGFILE"
383 >logfile directive</A
385 is being used and the following <A
386 HREF="../user-manual/config.html#DEBUG"
391 CLASS="LITERALLAYOUT"
392 >debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
393 debug 2 # show each connection status<br>
394 debug 4 # show I/O status<br>
395 debug 8 # show header parsing<br>
396 debug 128 # debug redirects<br>
397 debug 256 # debug GIF de-animation<br>
398 debug 512 # Common Log Format<br>
399 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
400 debug 4096 # Startup banner and warnings.<br>
401 debug 8192 # Non-fatal errors</P
403 If you are having trouble with a filter, please additionally enable
405 CLASS="LITERALLAYOUT"
406 >debug 64 # debug regular expression filters</P
408 If you are using Privoxy 3.0.17 or later and suspect that it interprets the
409 request or the response incorrectly, please enable
411 CLASS="LITERALLAYOUT"
412 >debug 32768 # log all data read from the network</P
414 Note that Privoxy log files may contain sensitive information so please don't
415 submit any logfiles you didn't read first. You can mask sensitive information
416 as long as it's clear that you removed something.
422 > You don't have to tell us your actual name when filing a problem
423 report, but if you don't, please use a nickname so we can differentiate
424 between your messages and the ones entered by other "anonymous" users that
425 may respond to your request if they have the same problem or already
426 found a solution. Note that due to spam the trackers may not always
427 allow to post without being logged into SourceForge. If that's the
428 case, you are still free to create a login that isn't directly linked
429 to your name, though.</P
431 > Please also check the status of your request a few days after submitting
432 it, as we may request additional information. If you use a SF id,
433 you should automatically get a mail when someone responds to your request.
434 Please don't bother to add an email address when using the tracker.
435 If you prefer to communicate through email, just use one of the mailing
439 HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
442 of the Privoxy User Manual</A
443 > also has helpful information
458 NAME="CONTACT-FEATURE"
459 >8.3. Request New Features</A
462 > You are welcome to submit ideas on new features or other proposals
463 for improvement through our feature request tracker at
465 HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
467 >http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
476 >8.4. Mailing Lists</A
479 >If you prefer to communicate through email, instead of using a web interface,
480 feel free to use one of the mailing lists.
481 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
482 users list. Technically interested users and people who wish to contribute to
483 the project are always welcome on the developers list.
484 You can find an overview of all <SPAN
487 >-related mailing lists,
488 including list archives, at:
490 HREF="http://sourceforge.net/mail/?group_id=11118"
492 >http://sourceforge.net/mail/?group_id=11118</A
501 SUMMARY="Footer navigation table"
512 HREF="webserver-update.html"
530 HREF="copyright.html"
540 >Update the Webserver</TD
550 >Privoxy Copyright, License and History</TD