For casual users, our support forum at SourceForge is probably best suited: http://sourceforge.net/tracker/?group_id=11118&atid=211118
, where the developers also hang around.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 @@ -185,7 +191,7 @@ CLASS="FILENAME" >default.action file, to http://sourceforge.net/tracker/?group_id=11118&atid=460288, @@ -222,7 +228,7 @@ NAME="CONTACT-BUGS" >
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 formAny 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). + 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
debug 64 # debug regular expression filters
+ If you using Privoxy 3.0.17 or later and suspect that it interprets the + request or the response incorrectly, please enable +debug 32768 # log all data read from the network
+ 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 + report, but if you don't, 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 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.
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! +>If you prefer to communicate through email, instead of using a web interface, +feel free to use one of the mailing lists. +To discuss issues that haven't been completely diagnosed, please use the Privoxy +users list. Technically interested users and people who wish to contribute to +the project are always welcome on the developers list. You can find an overview of all Privoxy