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.27 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.27 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="SUFFICIENT-INFORMATION"
100 >11.1. Please provide sufficient information</A
103 > A lot of support requests don't contain enough information and can't
104 be solved without a lot of back and forth which causes unnecessary
105 delays. Reading this section should help to prevent that.</P
107 > Before contacting us to report a problem, please try to verify that it is a
111 > problem, and not a browser or site problem
112 or documented behaviour that just happens to be different than what you expected.
115 HREF="http://config.privoxy.org/toggle?set=disable"
122 >, and see if the problem persists.</P
124 > If you are using your own custom configuration, please try the default
125 configuration to see if the problem is configuration related.
126 If you're having problems with a feature that is disabled by default,
127 please ask around on the mailing list if others can reproduce the problem.</P
129 > If you aren't using the latest Privoxy version, the problem may have been found
130 and fixed in the meantime. We would appreciate if you could take the time
132 HREF="https://www.privoxy.org/user-manual/installation.html"
135 to the latest version</A
136 > and verify that the problem still exists.</P
138 > Please be sure to provide the following information when reporting problems
139 or requesting support:</P
148 > version you are using.
153 > The operating system and versions you run
166 > The name, platform, and version of the <SPAN
170 you were using (e.g. <SPAN
172 >Internet Explorer v5.5</SPAN
178 > The URL where the problem occurred, or some way for us to duplicate the
181 >http://somesite.example.com/?somethingelse=123</TT
187 > Whether your version of <SPAN
194 > developers via SourceForge,
195 or if you got your copy somewhere else.
200 > Whether you are using <SPAN
204 another proxy such as <SPAN
208 temporary disable the other proxy to see if the symptoms change.
213 > Whether you are using a personal firewall product. If so, does
222 > Any other pertinent information to help identify the problem such as config
223 or log file excerpts (yes, you should have log file entries for each
224 action taken). To get a meaningful logfile, please make sure that the
226 HREF="../user-manual/config.html#LOGFILE"
228 >logfile directive</A
230 is being used and the following <A
231 HREF="../user-manual/config.html#DEBUG"
238 CLASS="LITERALLAYOUT"
239 >debug 1 # Log the destination for each request Privoxy let through.<br>
240 # See also debug 1024.<br>
241 debug 2 # show each connection status<br>
242 debug 4 # show I/O status<br>
243 debug 8 # show header parsing<br>
244 debug 128 # debug redirects<br>
245 debug 256 # debug GIF de-animation<br>
246 debug 512 # Common Log Format<br>
247 debug 1024 # Log the destination for requests Privoxy didn't let through,<br>
248 # and the reason why.<br>
249 debug 4096 # Startup banner and warnings.<br>
250 debug 8192 # Non-fatal errors<br>
251 debug 65536 # Log applying actions</P
253 > If you are having trouble with a filter, please additionally enable
256 CLASS="LITERALLAYOUT"
257 >debug 64 # debug regular expression filters</P
259 > If you suspect that Privoxy interprets the request or the response
260 incorrectly, please enable
263 CLASS="LITERALLAYOUT"
264 >debug 32768 # log all data read from the network</P
266 > It's easy for us to ignore log messages that aren't relevant but missing
267 log messages may make it impossible to investigate a problem. If you aren't
268 sure which of the debug directives are relevant, please just enable all of them
269 and let us worry about it.
272 > Note that Privoxy log files may contain sensitive information so please don't
273 submit any logfiles you didn't read first. You can mask sensitive information
274 as long as it's clear that you removed something.
279 > You don't have to tell us your actual name when filing a problem
280 report, but if you don't, please use a nickname so we can differentiate
281 between your messages and the ones entered by other "anonymous" users that
282 may respond to your request if they have the same problem or already
283 found a solution. Note that due to spam the trackers may not always
284 allow to post without being logged into SourceForge. If that's the
285 case, you are still free to create a login that isn't directly linked
286 to your name, though.</P
288 > Please also check the status of your request a few days after submitting
289 it, as we may request additional information. If you use a SF id,
290 you should automatically get a mail when someone responds to your request.
291 Please don't bother to add an email address when using the tracker.
292 If you prefer to communicate through email, just use one of the mailing
295 > If you are new to reporting problems, you might be interested in
297 HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
299 >How to Report Bugs Effectively</A
303 HREF="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
306 of the Privoxy User Manual</A
307 > also has helpful information
321 NAME="CONTACT-SUPPORT"
322 >11.2. Get Support</A
325 > All users are welcome to discuss their issues on the <A
326 HREF="https://lists.privoxy.org/mailman/listinfo/privoxy-users"
330 >, where the developers also hang around.</P
332 > Please don't send private support requests to individual Privoxy
333 developers, either use the mailing lists or the support trackers.</P
335 > If you have to contact a Privoxy developer directly for other reasons,
336 please send a real mail and do not bother with SourceForge's messaging
337 system. Answers to SourceForge messages are usually bounced by SourceForge's
338 mail server in which case the developer wasted time writing a response you
339 don't get. From your point of view it will look like your message has
340 been completely ignored, so this is frustrating for all parties involved.</P
342 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
343 addresses have to be accepted manually by a moderator. This may cause a
344 delay of several days and if you use a subject that doesn't clearly
345 mention Privoxy or one of its features, your message may be accidentally
346 discarded as spam.</P
348 > If you aren't subscribed, you should therefore spend a few seconds
349 to come up with a proper subject. Additionally you should make it clear
350 that you want to get CC'd. Otherwise some responses will be directed to
351 the mailing list only, and you won't see them.</P
359 >11.3. Reporting Problems</A
365 > for our purposes, come in two forms:</P
371 > Configuration issues, such as ads that slip through, or sites that
372 don't function properly due to one <SPAN
379 > or another being turned <SPAN
390 > in the programming code that makes up
394 >, such as that might cause a crash.
395 Documentation issues, for example spelling errors and unclear descriptions,
406 >11.3.1. Reporting Ads or Other Configuration Problems</A
409 > Please send feedback on ads that slipped through, innocent images that were
410 blocked, sites that don't work properly, and other configuration related problem of
416 HREF="https://sourceforge.net/tracker/?group_id=11118&atid=460288"
418 > https://sourceforge.net/tracker/?group_id=11118&atid=460288</A
420 the Actions File Tracker.</P
428 >11.3.2. Reporting Bugs</A
431 > Before reporting bugs, please make sure that the bug has <SPAN
435 >not already been submitted</I
438 and observe the additional hints at the top of the <A
439 HREF="https://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
443 >. If already submitted, please feel free to add any info to the
444 original report that might help to solve the issue.</P
452 NAME="SECURITY-CONTACT"
453 >11.4. Reporting security problems</A
456 > If you discovered a security problem or merely suspect that a bug might
457 be a security issue, please mail Fabian Keil <fk@fabiankeil.de>
458 (OpenPGP fingerprint: 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C).</P
460 > Usually you should get a response within a day, otherwise it's
461 likely that either your mail or the response didn't make it.
462 If that happens, please mail to the developer list to request a
471 >11.5. Mailing Lists</A
474 >If you prefer to communicate through email, instead of using a web interface,
475 feel free to use one of the mailing lists.
476 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
477 users list. Technically interested users and people who wish to contribute to
478 the project are always welcome on the developers list.
479 You can find an overview of all <SPAN
482 >-related mailing lists,
483 including list archives, at:
485 HREF="https://lists.privoxy.org/mailman/listinfo"
487 >https://lists.privoxy.org/mailman/listinfo</A
489 The lists hosted on privoxy.org have been created in 2016, the previously-used
490 lists hosted at SourceForge are deprecated but the archives may still be useful:
492 HREF="https://sourceforge.net/mail/?group_id=11118"
494 >https://sourceforge.net/mail/?group_id=11118</A
503 >11.6. SourceForge support trackers</A
508 HREF="https://sourceforge.net/tracker/?group_id=11118&atid=211118"
510 >SourceForge support trackers</A
512 may be used as well, but have various technical problems that are unlikely to
513 be fixed anytime soon. If you don't get a timely response, please try the
514 mailing list as well.</P
522 SUMMARY="Footer navigation table"
533 HREF="templates.html"
551 HREF="copyright.html"
561 >Privoxy's Template Files</TD
571 >Privoxy Copyright, License and History</TD