Contacting the developers, Bug Reporting and Feature Requests

We value your feedback. In fact, we rely on it to improve 6.1. Get Support6.1. Get Support

Please don't sent private support requests to individual Privoxy + developers, either use the mailing lists or the support trackers.

Note that the Privoxy mailing lists are moderated. Posts from unsubscribed + addresses have to be accepted manually by a moderator. This may cause a + delay of several days and if you use a subject that doesn't clearly + mention Privoxy or one of its features, your message may be accidentally + discarded as spam.

If you aren't subscribed, you should therefore spend a few seconds + to come up with a proper subject. Additionally you should make it clear + that you want to get CC'd. Otherwise some responses will be directed to + the mailing list only, and you won't see them.

6.2. Reporting Problems6.2. Reporting Problems

6.2.1. Reporting Ads or Other Configuration Problems6.2.1. Reporting Ads or Other Configuration Problems

Please send feedback on ads that slipped through, innocent images that were blocked, sites that don't work properly, and other configuration related problem of @@ -174,7 +191,7 @@ CLASS="FILENAME" >default.action file, to http://sourceforge.net/tracker/?group_id=11118&atid=460288, @@ -206,19 +223,12 @@ CLASS="SECT3" CLASS="SECT3" >6.2.2. Reporting Bugs6.2.2. Reporting Bugs

Please report all bugs only through our - bug tracker: +> Please report all bugs through our bug tracker: http://sourceforge.net/tracker/?group_id=11118&atid=111118.

and observe the additional hints at the top of the submit form. If already submitted, please feel free to add any info to the original report that might help to solve the issue.

- Please try to verify that it is a Please try to verify that it is a Privoxy bug, - and not a browser or site bug first. If unsure, + and not a browser or site bug or documented behaviour that just happens + to be different than what you expected. If unsure, try Privoxy, and see if the problem persists. - If you are using your own custom configuration, please try - the stock configs to see if the problem is configuration related.

, and see if the problem persists.

If you are using your own custom configuration, please try + the stock configs to see if the problem is configuration related. + If you're having problems with a feature that is disabled by default, + please ask around on the mailing list if others can reproduce the problem.

If not using the latest version, the bug may have been found +> If you aren't using the latest Privoxy version, the bug may have been found and fixed in the meantime. We would appreciate if you could take the time to upgrade to the latest version (or even the latest CVS snapshot) and verify - your bug.

Please be sure to provide the following information:

The exact Privoxy version of the proxy software +> version you are using (if you got the source from CVS, please also provide the source code revisions as shown in "uname -a" should do. +> should do, + in case of GNU/Linux, please also name the distribution.

Privoxy is one supplied - by the developers of Privoxy via SourceForge, - or somewhere else. +> developers via SourceForge, + or if you got your copy somewhere else.

Tor. If so, please try - disabling the other proxy. +>. If so, please + temporary disable the other proxy to see if the symptoms change.

Any other pertinent information to help identify the problem such as config or log file excerpts (yes, you should have log file entries for each - action taken). -

Please provide your SF login, or email address, in case we - need to contact you. + action taken). To get a meaningful logfile, please make sure that the + logfile directive + is being used and the following debug options are enabled: +

debug     1 # Log the destination for each request Privoxy let through. See also debug 1024.
+debug     2 # show each connection status
+debug     4 # show I/O status
+debug     8 # show header parsing
+debug   128 # debug redirects
+debug   256 # debug GIF de-animation
+debug   512 # Common Log Format
+debug  1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
+debug  4096 # Startup banner and warnings.
+debug  8192 # Non-fatal errors

+ If you are having trouble with a filter, please additionally enable +

debug 64 # debug regular expression filters

+ Note that Privoxy log files may contain sensitive information so please don't + submit any logfiles you didn't read first. You can mask sensitive information + as long as it's clear that you removed something.

You don't have to tell us your actual name when filing a problem + report, but please use a nickname so we can differentiate between + your messages and the ones entered by other "anonymous" users that + may respond to your request if they have the same problem or already + found a solution.

Please also check the status of your request a few days after submitting + it, as we may request additional information. If you use a SF id, + you should automatically get a mail when someone responds to your request.

The 6.3. Request New Features6.3. Request New Features

You are welcome to submit ideas on new features or other proposals for improvement through our feature request tracker at http://sourceforge.net/tracker/?atid=361118&group_id=11118.

6.4. Other6.4. Other

For any other issues, feel free to use the mailing lists. Technically interested users and people who wish to contribute to the project are also welcome on the developers list! @@ -495,4 +538,4 @@ VALIGN="top" >