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 Frequently Asked Questions"
11 HREF="index.html"><LINK
13 TITLE="Troubleshooting"
14 HREF="trouble.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 Frequently Asked Questions</TH
80 >6. 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 > If you have to contact a Privoxy developer directly for other reasons,
123 please send a real mail and do not bother with SourceForge's messaging
124 system. Answers to SourceForge messages are usually bounced by SourceForge's
125 mail server in which case the developer wasted time writing a response you
126 don't get. From your point of view it will look like your message has
127 been completely ignored, so this is frustrating for all parties involved.</P
129 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
130 addresses have to be accepted manually by a moderator. This may cause a
131 delay of several days and if you use a subject that doesn't clearly
132 mention Privoxy or one of its features, your message may be accidentally
133 discarded as spam.</P
135 > If you aren't subscribed, you should therefore spend a few seconds
136 to come up with a proper subject. Additionally you should make it clear
137 that you want to get CC'd. Otherwise some responses will be directed to
138 the mailing list only, and you won't see them.</P
146 >6.2. Reporting Problems</A
152 > for our purposes, come in two forms:</P
158 > Configuration issues, such as ads that slip through, or sites that
159 don't function properly due to one <SPAN
166 > or another being turned <SPAN
177 > in the programming code that makes up
181 >, such as that might cause a crash.
191 >6.2.1. Reporting Ads or Other Configuration Problems</A
194 > Please send feedback on ads that slipped through, innocent images that were
195 blocked, sites that don't work properly, and other configuration related problem of
201 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
203 > http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
205 the Actions File Tracker.</P
210 > files may occasionally be made
211 available based on your feedback. These will be announced on the <A
212 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
216 list and available from our the <A
217 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
222 HREF="http://sf.net/projects/ijbswa/"
233 >6.2.2. Reporting Bugs</A
236 > Please report all bugs through our bug tracker:
238 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
240 >http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
243 > Before doing so, please make sure that the bug has <SPAN
247 >not already been submitted</I
250 and observe the additional hints at the top of the <A
251 HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
255 >. If already submitted, please feel free to add any info to the
256 original report that might help to solve the issue.</P
258 > Please try to verify that it is a <SPAN
262 and not a browser or site bug or documented behaviour that just happens
263 to be different than what you expected. If unsure,
265 HREF="http://config.privoxy.org/toggle?set=disable"
272 >, and see if the problem persists.</P
274 > If you are using your own custom configuration, please try
275 the stock configs to see if the problem is configuration related.
276 If you're having problems with a feature that is disabled by default,
277 please ask around on the mailing list if others can reproduce the problem.</P
279 > If you aren't using the latest Privoxy version, the bug may have been found
280 and fixed in the meantime. We would appreciate if you could take the time
282 HREF="http://www.privoxy.org/user-manual/installation.html"
285 to the latest version</A
286 > (or even the latest CVS snapshot) and verify
287 that your bug still exists.</P
289 >Please be sure to provide the following information:</P
299 > version you are using
300 (if you got the source from CVS, please also provide the source code revisions
302 HREF="http://config.privoxy.org/show-version"
304 >http://config.privoxy.org/show-version</A
310 > The operating system and versions you run
318 >), if you are using a Unix flavor,
319 sending the output of <SPAN
323 in case of GNU/Linux, please also name the distribution.
328 > The name, platform, and version of the <SPAN
332 you were using (e.g. <SPAN
334 >Internet Explorer v5.5</SPAN
340 > The URL where the problem occurred, or some way for us to duplicate the
343 >http://somesite.example.com/?somethingelse=123</TT
349 > Whether your version of <SPAN
356 > developers via SourceForge,
357 or if you got your copy somewhere else.
362 > Whether you are using <SPAN
366 another proxy such as <SPAN
370 temporary disable the other proxy to see if the symptoms change.
375 > Whether you are using a personal firewall product. If so, does
384 > Any other pertinent information to help identify the problem such as config
385 or log file excerpts (yes, you should have log file entries for each
386 action taken). To get a meaningful logfile, please make sure that the
388 HREF="../user-manual/config.html#LOGFILE"
390 >logfile directive</A
392 is being used and the following <A
393 HREF="../user-manual/config.html#DEBUG"
398 CLASS="LITERALLAYOUT"
399 >debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
400 debug 2 # show each connection status<br>
401 debug 4 # show I/O status<br>
402 debug 8 # show header parsing<br>
403 debug 128 # debug redirects<br>
404 debug 256 # debug GIF de-animation<br>
405 debug 512 # Common Log Format<br>
406 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
407 debug 4096 # Startup banner and warnings.<br>
408 debug 8192 # Non-fatal errors</P
410 If you are having trouble with a filter, please additionally enable
412 CLASS="LITERALLAYOUT"
413 >debug 64 # debug regular expression filters</P
415 If you are using Privoxy 3.0.17 or later and suspect that it interprets the
416 request or the response incorrectly, please enable
418 CLASS="LITERALLAYOUT"
419 >debug 32768 # log all data read from the network</P
421 Note that Privoxy log files may contain sensitive information so please don't
422 submit any logfiles you didn't read first. You can mask sensitive information
423 as long as it's clear that you removed something.
429 > You don't have to tell us your actual name when filing a problem
430 report, but if you don't, please use a nickname so we can differentiate
431 between your messages and the ones entered by other "anonymous" users that
432 may respond to your request if they have the same problem or already
433 found a solution. Note that due to spam the trackers may not always
434 allow to post without being logged into SourceForge. If that's the
435 case, you are still free to create a login that isn't directly linked
436 to your name, though.</P
438 > Please also check the status of your request a few days after submitting
439 it, as we may request additional information. If you use a SF id,
440 you should automatically get a mail when someone responds to your request.
441 Please don't bother to add an email address when using the tracker.
442 If you prefer to communicate through email, just use one of the mailing
446 HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
449 of the Privoxy User Manual</A
450 > also has helpful information
465 NAME="CONTACT-FEATURE"
466 >6.3. Request New Features</A
469 > You are welcome to submit ideas on new features or other proposals
470 for improvement through our feature request tracker at
472 HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
474 >http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
483 >6.4. Mailing Lists</A
486 >If you prefer to communicate through email, instead of using a web interface,
487 feel free to use one of the mailing lists.
488 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
489 users list. Technically interested users and people who wish to contribute to
490 the project are always welcome on the developers list.
491 You can find an overview of all <SPAN
494 >-related mailing lists,
495 including list archives, at:
497 HREF="http://sourceforge.net/mail/?group_id=11118"
499 >http://sourceforge.net/mail/?group_id=11118</A
508 SUMMARY="Footer navigation table"
537 HREF="copyright.html"
557 >Privoxy Copyright, License and History</TD