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:
+ the following hints, so we can provide you with the best support.A lot of support requests don't contain enough information and can't + be solved without a lot of back and forth which causes unnecessary + delays. Reading this section should help to prevent that.
+ +Before contacting us to report a problem, please try to verify that + it is a Privoxy problem, and not a + browser or site problem or documented behaviour that just happens to be + different than what you expected. If unsure, try toggling + off Privoxy, and see if the + problem persists.
+ +If you are using your own custom configuration, please try the + default configuration 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 you aren't using the latest Privoxy version, the problem may have + been found and fixed in the meantime. We would appreciate if you could + take the time to upgrade to the latest version and verify that the problem + still exists.
+ +Please be sure to provide the following information when reporting + problems or requesting support:
+ +The exact Privoxy version you + are using.
+The operating system and versions you run Privoxy on, e.g. Windows XP SP2.
+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 Privoxy + developers via SourceForge, or if you got your copy somewhere + else.
+Whether you are using Privoxy + together with another proxy such as Tor. If so, please temporary disable the other + proxy to see if the symptoms change.
+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). To get a meaningful logfile, please + make sure that the logfile directive is being used and the following + debug + options are enabled (all of them):
+ +
+ 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
If + you are 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
+ +It's easy for us to ignore log messages that aren't relevant but + missing log messages may make it impossible to investigate a + problem. If you aren't sure which of the debug directives are + relevant, please just enable all of them and let us worry about + it.
+ +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 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. Note that due to spam the trackers may not + always allow to post without being logged into SourceForge. If that's + the case, you are still free to create a login that isn't directly + linked to your name, though.
+ +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. Please don't bother to add an email address when using + the tracker. If you prefer to communicate through email, just use one + of the mailing lists directly.
+ +If you are new to reporting problems, you might be interested in + How to Report Bugs Effectively.
+ +The appendix of the Privoxy User Manual also has helpful + information on understanding actions, and + action debugging.
+For casual users, our
"Problems" for our purposes, come in two
@@ -109,7 +265,7 @@
Please send feedback on ads that slipped through, innocent images
@@ -132,7 +288,7 @@
Please report all bugs through our bug tracker: 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 Privoxy bug, and not a browser or site bug or
- documented behaviour that just happens to be different than what you
- expected. 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
- 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 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 that your bug still exists. Please be sure to provide the following information: The exact Privoxy version you
- are using (if you got the source from CVS, please also provide
- the source code revisions as shown in http://config.privoxy.org/show-version). The operating system and versions you run Privoxy on, (e.g. Windows XP SP2), if you are using a Unix
- flavor, sending the output of "uname
- -a" should do, in case of GNU/Linux, please also name the
- distribution. 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 Privoxy developers via SourceForge, or if
- you got your copy somewhere else. Whether you are using Privoxy
- in tandem with another proxy such as Tor. If so, please temporary disable the
- other proxy to see if the symptoms change. 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). 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 64 # debug regular expression filters
- debug 32768 # log all data read from the network You don't have to tell us your actual name when filing a problem
- 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. Note that due to spam the
- trackers may not always allow to post without being logged into
- SourceForge. If that's the case, you are still free to create a login
- that isn't directly linked to your name, though. 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. Please don't bother to add an email address when using
- the tracker. If you prefer to communicate through email, just use one
- of the mailing lists directly. If you are new to reporting problems, you might be interested in
- How to Report Bugs Effectively. The appendix of the Privoxy User Manual also has
- helpful information on understanding actions, and action
- debugging.11.2. Reporting
+
11.3. Reporting
Problems
11.2.1.
+
11.3.1.
Reporting Ads or Other Configuration Problems
11.2.2.
+
11.3.2.
Reporting Bugs
-
-
-
-
- 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