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="SUFFICIENT-INFORMATION"
96 >6.1. Please provide sufficient information</A
99 > A lot of support requests don't contain enough information and can't
100 be solved without a lot of back and forth which causes unnecessary
101 delays. Reading this section should help to prevent that.</P
103 > Before contacting us to report a problem, please try to verify that it is a
107 > problem, and not a browser or site problem
108 or documented behaviour that just happens to be different than what you expected.
111 HREF="http://config.privoxy.org/toggle?set=disable"
118 >, and see if the problem persists.</P
120 > If you are using your own custom configuration, please try the default
121 configuration to see if the problem is configuration related.
122 If you're having problems with a feature that is disabled by default,
123 please ask around on the mailing list if others can reproduce the problem.</P
125 > If you aren't using the latest Privoxy version, the problem may have been found
126 and fixed in the meantime. We would appreciate if you could take the time
128 HREF="https://www.privoxy.org/user-manual/installation.html"
131 to the latest version</A
132 > and verify that the problem still exists.</P
134 > Please be sure to provide the following information when reporting problems
135 or requesting support:</P
144 > version you are using.
149 > The operating system and versions you run
162 > The name, platform, and version of the <SPAN
166 you were using (e.g. <SPAN
168 >Internet Explorer v5.5</SPAN
174 > The URL where the problem occurred, or some way for us to duplicate the
177 >http://somesite.example.com/?somethingelse=123</TT
183 > Whether your version of <SPAN
190 > developers via SourceForge,
191 or if you got your copy somewhere else.
196 > Whether you are using <SPAN
200 another proxy such as <SPAN
204 temporary disable the other proxy to see if the symptoms change.
209 > Whether you are using a personal firewall product. If so, does
218 > Any other pertinent information to help identify the problem such as config
219 or log file excerpts (yes, you should have log file entries for each
220 action taken). To get a meaningful logfile, please make sure that the
222 HREF="../user-manual/config.html#LOGFILE"
224 >logfile directive</A
226 is being used and the following <A
227 HREF="../user-manual/config.html#DEBUG"
234 CLASS="LITERALLAYOUT"
235 >debug 1 # Log the destination for each request Privoxy let through.<br>
236 # See also debug 1024.<br>
237 debug 2 # show each connection status<br>
238 debug 4 # show I/O status<br>
239 debug 8 # show header parsing<br>
240 debug 128 # debug redirects<br>
241 debug 256 # debug GIF de-animation<br>
242 debug 512 # Common Log Format<br>
243 debug 1024 # Log the destination for requests Privoxy didn't let through,<br>
244 # and the reason why.<br>
245 debug 4096 # Startup banner and warnings.<br>
246 debug 8192 # Non-fatal errors<br>
247 debug 65536 # Log applying actions</P
249 > If you are having trouble with a filter, please additionally enable
252 CLASS="LITERALLAYOUT"
253 >debug 64 # debug regular expression filters</P
255 > If you suspect that Privoxy interprets the request or the response
256 incorrectly, please enable
259 CLASS="LITERALLAYOUT"
260 >debug 32768 # log all data read from the network</P
262 > It's easy for us to ignore log messages that aren't relevant but missing
263 log messages may make it impossible to investigate a problem. If you aren't
264 sure which of the debug directives are relevant, please just enable all of them
265 and let us worry about it.
268 > Note that Privoxy log files may contain sensitive information so please don't
269 submit any logfiles you didn't read first. You can mask sensitive information
270 as long as it's clear that you removed something.
275 > You don't have to tell us your actual name when filing a problem
276 report, but if you don't, please use a nickname so we can differentiate
277 between your messages and the ones entered by other "anonymous" users that
278 may respond to your request if they have the same problem or already
279 found a solution. Note that due to spam the trackers may not always
280 allow to post without being logged into SourceForge. If that's the
281 case, you are still free to create a login that isn't directly linked
282 to your name, though.</P
284 > Please also check the status of your request a few days after submitting
285 it, as we may request additional information. If you use a SF id,
286 you should automatically get a mail when someone responds to your request.
287 Please don't bother to add an email address when using the tracker.
288 If you prefer to communicate through email, just use one of the mailing
291 > If you are new to reporting problems, you might be interested in
293 HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
295 >How to Report Bugs Effectively</A
299 HREF="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
302 of the Privoxy User Manual</A
303 > also has helpful information
317 NAME="CONTACT-SUPPORT"
321 > All users are welcome to discuss their issues on the <A
322 HREF="https://lists.privoxy.org/mailman/listinfo/privoxy-users"
326 >, where the developers also hang around.</P
328 > Please don't send private support requests to individual Privoxy
329 developers, either use the mailing lists or the support trackers.</P
331 > If you have to contact a Privoxy developer directly for other reasons,
332 please send a real mail and do not bother with SourceForge's messaging
333 system. Answers to SourceForge messages are usually bounced by SourceForge's
334 mail server in which case the developer wasted time writing a response you
335 don't get. From your point of view it will look like your message has
336 been completely ignored, so this is frustrating for all parties involved.</P
338 > Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
339 addresses have to be accepted manually by a moderator. This may cause a
340 delay of several days and if you use a subject that doesn't clearly
341 mention Privoxy or one of its features, your message may be accidentally
342 discarded as spam.</P
344 > If you aren't subscribed, you should therefore spend a few seconds
345 to come up with a proper subject. Additionally you should make it clear
346 that you want to get CC'd. Otherwise some responses will be directed to
347 the mailing list only, and you won't see them.</P
355 >6.3. Reporting Problems</A
361 > for our purposes, come in two forms:</P
367 > Configuration issues, such as ads that slip through, or sites that
368 don't function properly due to one <SPAN
375 > or another being turned <SPAN
386 > in the programming code that makes up
390 >, such as that might cause a crash.
391 Documentation issues, for example spelling errors and unclear descriptions,
402 >6.3.1. Reporting Ads or Other Configuration Problems</A
405 > Please send feedback on ads that slipped through, innocent images that were
406 blocked, sites that don't work properly, and other configuration related problem of
412 HREF="https://sourceforge.net/tracker/?group_id=11118&atid=460288"
414 > https://sourceforge.net/tracker/?group_id=11118&atid=460288</A
416 the Actions File Tracker.</P
424 >6.3.2. Reporting Bugs</A
427 > Before reporting bugs, please make sure that the bug has <SPAN
431 >not already been submitted</I
434 and observe the additional hints at the top of the <A
435 HREF="https://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
439 >. If already submitted, please feel free to add any info to the
440 original report that might help to solve the issue.</P
448 NAME="SECURITY-CONTACT"
449 >6.4. Reporting security problems</A
452 > If you discovered a security problem or merely suspect that a bug might
453 be a security issue, please mail Fabian Keil <fk@fabiankeil.de>
454 (OpenPGP fingerprint: 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C).</P
456 > Usually you should get a response within a day, otherwise it's
457 likely that either your mail or the response didn't make it.
458 If that happens, please mail to the developer list to request a
467 >6.5. Mailing Lists</A
470 >If you prefer to communicate through email, instead of using a web interface,
471 feel free to use one of the mailing lists.
472 To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
473 users list. Technically interested users and people who wish to contribute to
474 the project are always welcome on the developers list.
475 You can find an overview of all <SPAN
478 >-related mailing lists,
479 including list archives, at:
481 HREF="https://lists.privoxy.org/mailman/listinfo"
483 >https://lists.privoxy.org/mailman/listinfo</A
485 The lists hosted on privoxy.org have been created in 2016, the previously-used
486 lists hosted at SourceForge are deprecated but the archives may still be useful:
488 HREF="https://sourceforge.net/mail/?group_id=11118"
490 >https://sourceforge.net/mail/?group_id=11118</A
499 >6.6. SourceForge support trackers</A
504 HREF="https://sourceforge.net/tracker/?group_id=11118&atid=211118"
506 >SourceForge support trackers</A
508 may be used as well, but have various technical problems that are unlikely to
509 be fixed anytime soon. If you don't get a timely response, please try the
510 mailing list as well.</P
518 SUMMARY="Footer navigation table"
547 HREF="copyright.html"
567 >Privoxy Copyright, License and History</TD