/*********************************************************************
*
- * File : doc/source/readme.sgml
+ * File : README
*
- * Purpose : README file to give a short intro.
+ * Purpose : Give a short intro about Privoxy.
*
- * Copyright : Written by and Copyright (C) 2001-2020 the
+ * Copyright : Written by and Copyright (C) 2001-2021 the
* Privoxy team. https://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
*
*********************************************************************/
-This README is included with the development version of Privoxy 3.0.30. See
+This README is included with the development version of Privoxy 3.0.33. See
https://www.privoxy.org/ for more information. The current code maturity level
is "UNRELEASED", but seems stable to us :).
* 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 your version of Privoxy is one supplied by the Privoxy developers,
+ 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.
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.
+ debug 1 # Log the destination for each request. See also debug 1024.
# See also debug 1024.
debug 2 # show each connection status
- debug 4 # show I/O status
+ debug 4 # show tagging-related messages
debug 8 # show header parsing
debug 128 # debug redirects
debug 256 # debug GIF de-animation
debug 64 # debug regular expression filters
If you suspect that Privoxy interprets the request or the response
- incorrectly, please enable
+ incorrectly, please enable additionally
debug 32768 # log all data read from the network
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.
+ Please clear the browser cache before reproducing the problem.
+
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
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.