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
9 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
11 TITLE="Privoxy 3.0.17 User Manual"
12 HREF="index.html"><LINK
14 TITLE="Privoxy's Template Files"
15 HREF="templates.html"><LINK
17 TITLE="Privoxy Copyright, License and History"
18 HREF="copyright.html"><LINK
21 HREF="../p_doc.css"><META
22 HTTP-EQUIV="Content-Type"
25 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
37 SUMMARY="Header navigation table"
46 >Privoxy 3.0.17 User Manual</TH
83 >11. Contacting the Developers, Bug Reporting and Feature
87 > We value your feedback. In fact, we rely on it to improve
91 > and its configuration.
92 However, please note the following hints, so we can
93 provide you with the best support:</P
99 NAME="CONTACT-SUPPORT"
100 >11.1. Get Support</A
103 > For casual users, our
105 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
107 >support forum at SourceForge</A
109 is probably best suited:
111 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
113 >http://sourceforge.net/tracker/?group_id=11118&atid=211118</A
116 > All users are of course welcome to discuss their issues on the <A
117 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
121 >, where the developers also hang around.</P
123 > Please don't sent private support requests to individual Privoxy
124 developers, either use the mailing lists or the support trackers.</P
126 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
127 addresses have to be accepted manually by a moderator. This may cause a
128 delay of several days and if you use a subject that doesn't clearly
129 mention Privoxy or one of its features, your message may be accidentally
130 discarded as spam.</P
132 > If you aren't subscribed, you should therefore spend a few seconds
133 to come up with a proper subject. Additionally you should make it clear
134 that you want to get CC'd. Otherwise some responses will be directed to
135 the mailing list only, and you won't see them.</P
143 >11.2. Reporting Problems</A
149 > for our purposes, come in two forms:</P
155 > Configuration issues, such as ads that slip through, or sites that
156 don't function properly due to one <SPAN
163 > or another being turned <SPAN
174 > in the programming code that makes up
178 >, such as that might cause a crash.
188 >11.2.1. Reporting Ads or Other Configuration Problems</A
191 > Please send feedback on ads that slipped through, innocent images that were
192 blocked, sites that don't work properly, and other configuration related problem of
198 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
200 > http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
202 the Actions File Tracker.</P
207 > files may occasionally be made
208 available based on your feedback. These will be announced on the <A
209 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
213 list and available from our the <A
214 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
219 HREF="http://sf.net/projects/ijbswa/"
230 >11.2.2. Reporting Bugs</A
233 > Please report all bugs through our bug tracker:
235 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
237 >http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
240 > Before doing so, please make sure that the bug has <SPAN
244 >not already been submitted</I
247 and observe the additional hints at the top of the <A
248 HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
252 >. If already submitted, please feel free to add any info to the
253 original report that might help to solve the issue.</P
255 > Please try to verify that it is a <SPAN
259 and not a browser or site bug or documented behaviour that just happens
260 to be different than what you expected. If unsure,
262 HREF="http://config.privoxy.org/toggle?set=disable"
269 >, and see if the problem persists.</P
271 > If you are using your own custom configuration, please try
272 the stock configs to see if the problem is configuration related.
273 If you're having problems with a feature that is disabled by default,
274 please ask around on the mailing list if others can reproduce the problem.</P
276 > If you aren't using the latest Privoxy version, the bug may have been found
277 and fixed in the meantime. We would appreciate if you could take the time
279 HREF="http://www.privoxy.org/user-manual/installation.html"
282 to the latest version</A
283 > (or even the latest CVS snapshot) and verify
284 that your bug still exists.</P
286 >Please be sure to provide the following information:</P
296 > version you are using
297 (if you got the source from CVS, please also provide the source code revisions
299 HREF="http://config.privoxy.org/show-version"
301 >http://config.privoxy.org/show-version</A
307 > The operating system and versions you run
315 >), if you are using a Unix flavor,
316 sending the output of <SPAN
320 in case of GNU/Linux, please also name the distribution.
325 > The name, platform, and version of the <SPAN
329 you were using (e.g. <SPAN
331 >Internet Explorer v5.5</SPAN
337 > The URL where the problem occurred, or some way for us to duplicate the
340 >http://somesite.example.com/?somethingelse=123</TT
346 > Whether your version of <SPAN
353 > developers via SourceForge,
354 or if you got your copy somewhere else.
359 > Whether you are using <SPAN
363 another proxy such as <SPAN
367 temporary disable the other proxy to see if the symptoms change.
372 > Whether you are using a personal firewall product. If so, does
381 > Any other pertinent information to help identify the problem such as config
382 or log file excerpts (yes, you should have log file entries for each
383 action taken). To get a meaningful logfile, please make sure that the
385 HREF="../user-manual/config.html#LOGFILE"
387 >logfile directive</A
389 is being used and the following <A
390 HREF="../user-manual/config.html#DEBUG"
395 CLASS="LITERALLAYOUT"
396 >debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
397 debug 2 # show each connection status<br>
398 debug 4 # show I/O status<br>
399 debug 8 # show header parsing<br>
400 debug 128 # debug redirects<br>
401 debug 256 # debug GIF de-animation<br>
402 debug 512 # Common Log Format<br>
403 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
404 debug 4096 # Startup banner and warnings.<br>
405 debug 8192 # Non-fatal errors</P
407 If you are having trouble with a filter, please additionally enable
409 CLASS="LITERALLAYOUT"
410 >debug 64 # debug regular expression filters</P
412 If you are using Privoxy 3.0.17 or later and suspect that it interprets the
413 request or the response incorrectly, please enable
415 CLASS="LITERALLAYOUT"
416 >debug 32768 # log all data read from the network</P
418 Note that Privoxy log files may contain sensitive information so please don't
419 submit any logfiles you didn't read first. You can mask sensitive information
420 as long as it's clear that you removed something.
426 > You don't have to tell us your actual name when filing a problem
427 report, but if you don't, please use a nickname so we can differentiate
428 between your messages and the ones entered by other "anonymous" users that
429 may respond to your request if they have the same problem or already
430 found a solution. Note that due to spam the trackers may not always
431 allow to post without being logged into SourceForge. If that's the
432 case, you are still free to create a login that isn't directly linked
433 to your name, though.</P
435 > Please also check the status of your request a few days after submitting
436 it, as we may request additional information. If you use a SF id,
437 you should automatically get a mail when someone responds to your request.
438 Please don't bother to add an email address when using the tracker.
439 If you prefer to communicate through email, just use one of the mailing
443 HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
446 of the Privoxy User Manual</A
447 > also has helpful information
462 NAME="CONTACT-FEATURE"
463 >11.3. Request New Features</A
466 > You are welcome to submit ideas on new features or other proposals
467 for improvement through our feature request tracker at
469 HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
471 >http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
480 >11.4. Mailing Lists</A
483 >If you prefer to communicate through email, instead of using a web interface,
484 feel free to use one of the mailing lists.
485 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
486 users list. Technically interested users and people who wish to contribute to
487 the project are always welcome on the developers list.
488 You can find an overview of all <SPAN
491 >-related mailing lists,
492 including list archives, at:
494 HREF="http://sourceforge.net/mail/?group_id=11118"
496 >http://sourceforge.net/mail/?group_id=11118</A
505 SUMMARY="Footer navigation table"
516 HREF="templates.html"
534 HREF="copyright.html"
544 >Privoxy's Template Files</TD
554 >Privoxy Copyright, License and History</TD