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.18 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.18 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 > If you have to contact a Privoxy developer directly for other reasons,
127 please send a real mail and do not bother with SourceForge's messaging
128 system. Answers to SourceForge messages are usually bounced by SourceForge's
129 mail server in which case the developer wasted time writing a response you
130 don't get. From your point of view it will look like your message has
131 been completely ignored, so this is frustrating for all parties involved.</P
133 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
134 addresses have to be accepted manually by a moderator. This may cause a
135 delay of several days and if you use a subject that doesn't clearly
136 mention Privoxy or one of its features, your message may be accidentally
137 discarded as spam.</P
139 > If you aren't subscribed, you should therefore spend a few seconds
140 to come up with a proper subject. Additionally you should make it clear
141 that you want to get CC'd. Otherwise some responses will be directed to
142 the mailing list only, and you won't see them.</P
150 >11.2. Reporting Problems</A
156 > for our purposes, come in two forms:</P
162 > Configuration issues, such as ads that slip through, or sites that
163 don't function properly due to one <SPAN
170 > or another being turned <SPAN
181 > in the programming code that makes up
185 >, such as that might cause a crash.
195 >11.2.1. Reporting Ads or Other Configuration Problems</A
198 > Please send feedback on ads that slipped through, innocent images that were
199 blocked, sites that don't work properly, and other configuration related problem of
205 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
207 > http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
209 the Actions File Tracker.</P
214 > files may occasionally be made
215 available based on your feedback. These will be announced on the <A
216 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
220 list and available from our the <A
221 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
226 HREF="http://sf.net/projects/ijbswa/"
237 >11.2.2. Reporting Bugs</A
240 > Please report all bugs through our bug tracker:
242 HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
244 >http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
247 > Before doing so, please make sure that the bug has <SPAN
251 >not already been submitted</I
254 and observe the additional hints at the top of the <A
255 HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
259 >. If already submitted, please feel free to add any info to the
260 original report that might help to solve the issue.</P
262 > Please try to verify that it is a <SPAN
266 and not a browser or site bug or documented behaviour that just happens
267 to be different than what you expected. If unsure,
269 HREF="http://config.privoxy.org/toggle?set=disable"
276 >, and see if the problem persists.</P
278 > If you are using your own custom configuration, please try
279 the stock configs to see if the problem is configuration related.
280 If you're having problems with a feature that is disabled by default,
281 please ask around on the mailing list if others can reproduce the problem.</P
283 > If you aren't using the latest Privoxy version, the bug may have been found
284 and fixed in the meantime. We would appreciate if you could take the time
286 HREF="http://www.privoxy.org/user-manual/installation.html"
289 to the latest version</A
290 > (or even the latest CVS snapshot) and verify
291 that your bug still exists.</P
293 >Please be sure to provide the following information:</P
303 > version you are using
304 (if you got the source from CVS, please also provide the source code revisions
306 HREF="http://config.privoxy.org/show-version"
308 >http://config.privoxy.org/show-version</A
314 > The operating system and versions you run
322 >), if you are using a Unix flavor,
323 sending the output of <SPAN
327 in case of GNU/Linux, please also name the distribution.
332 > The name, platform, and version of the <SPAN
336 you were using (e.g. <SPAN
338 >Internet Explorer v5.5</SPAN
344 > The URL where the problem occurred, or some way for us to duplicate the
347 >http://somesite.example.com/?somethingelse=123</TT
353 > Whether your version of <SPAN
360 > developers via SourceForge,
361 or if you got your copy somewhere else.
366 > Whether you are using <SPAN
370 another proxy such as <SPAN
374 temporary disable the other proxy to see if the symptoms change.
379 > Whether you are using a personal firewall product. If so, does
388 > Any other pertinent information to help identify the problem such as config
389 or log file excerpts (yes, you should have log file entries for each
390 action taken). To get a meaningful logfile, please make sure that the
392 HREF="../user-manual/config.html#LOGFILE"
394 >logfile directive</A
396 is being used and the following <A
397 HREF="../user-manual/config.html#DEBUG"
402 CLASS="LITERALLAYOUT"
403 >debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
404 debug 2 # show each connection status<br>
405 debug 4 # show I/O status<br>
406 debug 8 # show header parsing<br>
407 debug 128 # debug redirects<br>
408 debug 256 # debug GIF de-animation<br>
409 debug 512 # Common Log Format<br>
410 debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
411 debug 4096 # Startup banner and warnings.<br>
412 debug 8192 # Non-fatal errors</P
414 If you are having trouble with a filter, please additionally enable
416 CLASS="LITERALLAYOUT"
417 >debug 64 # debug regular expression filters</P
419 If you are using Privoxy 3.0.17 or later and suspect that it interprets the
420 request or the response incorrectly, please enable
422 CLASS="LITERALLAYOUT"
423 >debug 32768 # log all data read from the network</P
425 Note that Privoxy log files may contain sensitive information so please don't
426 submit any logfiles you didn't read first. You can mask sensitive information
427 as long as it's clear that you removed something.
433 > You don't have to tell us your actual name when filing a problem
434 report, but if you don't, please use a nickname so we can differentiate
435 between your messages and the ones entered by other "anonymous" users that
436 may respond to your request if they have the same problem or already
437 found a solution. Note that due to spam the trackers may not always
438 allow to post without being logged into SourceForge. If that's the
439 case, you are still free to create a login that isn't directly linked
440 to your name, though.</P
442 > Please also check the status of your request a few days after submitting
443 it, as we may request additional information. If you use a SF id,
444 you should automatically get a mail when someone responds to your request.
445 Please don't bother to add an email address when using the tracker.
446 If you prefer to communicate through email, just use one of the mailing
450 HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
453 of the Privoxy User Manual</A
454 > also has helpful information
469 NAME="CONTACT-FEATURE"
470 >11.3. Request New Features</A
473 > You are welcome to submit ideas on new features or other proposals
474 for improvement through our feature request tracker at
476 HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
478 >http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
487 >11.4. Mailing Lists</A
490 >If you prefer to communicate through email, instead of using a web interface,
491 feel free to use one of the mailing lists.
492 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
493 users list. Technically interested users and people who wish to contribute to
494 the project are always welcome on the developers list.
495 You can find an overview of all <SPAN
498 >-related mailing lists,
499 including list archives, at:
501 HREF="http://sourceforge.net/mail/?group_id=11118"
503 >http://sourceforge.net/mail/?group_id=11118</A
512 SUMMARY="Footer navigation table"
523 HREF="templates.html"
541 HREF="copyright.html"
551 >Privoxy's Template Files</TD
561 >Privoxy Copyright, License and History</TD