We value your feedback. In fact, we rely on it to improve
Privoxy and its configuration.
However, please note the following hints, so we can
provide you with the best support:
Get Support
For casual users, our
support forum at SourceForge
is probably best suited:
http://sourceforge.net/tracker/?group_id=11118&atid=211118
All users are of course welcome to discuss their issues on the users
mailing list, where the developers also hang around.
Reporting Problems
Problems
for our purposes, come in two forms:
Configuration issues, such as ads that slip through, or sites that
don't function properly due to one Privoxy
action
or another being turned on
.
Bugs
in the programming code that makes up
Privoxy, such as that might cause a crash.
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
default.action file, to the
http://sourceforge.net/tracker/?group_id=11118&atid=460288,
the Actions File Tracker.
New, improved default.action files may occasionally be made
available based on your feedback. These will be announced on the ijbswa-announce
list and available from our the files section of
our project page.
Reporting Bugs
Please report all bugs only through our
bug tracker:
http://sourceforge.net/tracker/?group_id=11118&atid=111118.
Before doing so, please make sure that the bug has not already been submitted
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 solve the issue.
Please try to verify that it is a Privoxy bug,
and not a browser or site bug first. If unsure,
try toggling
off 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.
If not using the latest 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
(if you got the source from CVS, please also give the date).
The operating system and verions you run
Privoxy on, (e.g. Windows
XP).
The name, platform, and version of the browser
you were using (e.g. Internet Explorer v5.5 for Mac).
The URL where the problem occurred, or some way for us to duplicate the
problem (e.g. http://somesite.example.com?somethingelse=123).
Whether your version of Privoxy is one supplied
by the developers of Privoxy via SourceForge,
or somewhere else.
Whether you are using Privoxy in tandem with
another proxy such as TOR. If so, please try
disabling the other proxy.
Whether you are using a personal firewall product. If so, does
Privoxy work without it?
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.
The appendix
of the user manual also has helpful information
on understanding actions, and action debugging.
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.
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!
You can find an overview of all Privoxy-related mailing lists,
including list archives, at:
http://sourceforge.net/mail/?group_id=11118.