* this file. If not, you can view it at
* http://www.gnu.org/copyleft/gpl.html
* or write to the Free Software Foundation, Inc.,
- * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 ,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
* USA
*
*********************************************************************/
-This README is included with the development version of Privoxy 3.0.4. See
-http://www.privoxy.org/ for more information. The current code maturity level
-is "beta", but seems stable to us :).
+This README is included with Privoxy > 3.0.6 -> 3.0.7.
+See http://www.privoxy.org/ for more information. The current code maturity
+level is "unknown". Development work is in progress. There may be new
+features, bugs, partially working aspects, etc, all of which may not be
+documented. Use 3.0.6 for production systems and where stability is necessary.
+Please report any problems.
-------------------------------------------------------------------------------
1. IMPORTANT CHANGES
-BIG NEWS! 2006, Privoxy 3.0.4 is released. This is a significant upgrade with
-many new and enhanced features, and many bugs fixed. There are fifteen new
-actions available, and several actions have enhanced capabilities. Multiple
-filter files are now supported as well. See the "What's New" section and the
-"Upgrader's Notes" in the User Manual for details and specifics.
+NEWS! November 2006, Privoxy 3.0.6 is released. This is a significant upgrade
+with many new and enhanced features, and many bugs fixed. It is also the first
+stable release in quite some time. There are fifteen new actions available, and
+several actions have enhanced capabilities. Multiple filter files are now
+supported as well. There are many improvements and refinements. See the "What's
+New" section and the "Upgrader's Notes" in the User Manual for details and
+specifics. Preliminary work on 3.0.7 is already underway.
+
+NEWS! September 2006, Privoxy 3.0.5 BETA is released. This is a significant
+upgrade with many new and enhanced features, and many bugs fixed.
+
+There was and will not be an official 3.0.4 release. This release cycle was
+used to gather our thoughts, play with some new ideas and refine some old ones.
+It will remain a development cycle with no actual release. 3.0.5 is the fruit
+of these efforts.
NEWS! January 2004, Privoxy 3.0.3 is released. This is the another maintenance
release of Privoxy which fixes more bugs, further refines the configuration and
works around some known third-party problems. See the ChangeLog for complete
details. Upgrading from 3.0.2 is recommended.
-NEWS! March 2003, Privoxy 3.0.2 is released. This is the first maintenance
-release of Privoxy. There are no significant new features in this release. Some
-bugs are fixed, and some existing features have been enhanced. See ChangeLog
-for details. Upgrading from 3.0.0 is recommended.
-
-REALLY BIG NEWS! August 2002: The long-awaited, oft-delayed stable version of
-Privoxy 3.0 is finally released! This is way behind schedule, but better late
-than never. The developers all hope the wait was worth it.
-
-NEWS! As of 03/24/02, the name of this project has been changed from ijbswa/
-Junkbuster to Privoxy. This is reflected in many of the included files.
-
-IMPORTANT! READ! Configuration Change as of 17 Mar 2002: The default listening
-port is now 8118 due to conflicts with port 8000 assignment. You will need to
-change your browser if upgrading!!! And maybe firewall, etc.
-
-------------------------------------------------------------------------------
2. INSTALL
file named 'config' in the current directory (except Win32 which will look for
'config.txt'). If no config_file is found, Privoxy will fail to start.
-Or for Red Hat based distributions: /etc/rc.d/init.d/privoxy start
-
-Or for SuSE: /etc/rc.d/privoxy start
+Or for Red Hat and Fedora based distributions: /etc/rc.d/init.d/privoxy start
Or Debian: /etc/init.d/privoxy start
'user.filter'. 'user.action' and 'user.filter' are for personal and local
configuration preferences. These are all well commented. Most of the magic is
in '*.action' files. 'user.action' should be used for any actions
-customizations. On Unix-like systems, these files are installed in /etc/
-privoxy. On Windows, then wherever the executable itself is installed. There
-are many significant changes and advances from earlier versions. The User
+customizations. On Unix-like systems, these files are typically installed in /
+etc/privoxy. On Windows, then wherever the executable itself is installed.
+There are many significant changes and advances from earlier versions. The User
Manual has an explanation of all configuration options, and examples: http://
www.privoxy.org/user-manual/.
The actions list can be configured via the web interface accessed via http://
p.p/, as well other options.
-All configuration files are subject to unannounced changes during the
-development process.
-
-------------------------------------------------------------------------------
5. DOCUMENTATION
-There should be documentation in the 'doc' subdirectory, but it may not be
-completed at this point. In particular, see the User Manual there, the FAQ, and
-those interested in Privoxy development, should look at developer-manual.
+There should be documentation in the 'doc' subdirectory. In particular, see the
+User Manual there, the FAQ, and those interested in Privoxy development, should
+look at developer-manual.
-The most up to date source of information on the current development version,
-may still be either comments in the source code, or the included configuration
-files. The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter' in
-the top-level source directory.
+The source and configuration files are all well commented. The main
+configuration files are: 'config', 'default.action', and 'default.filter'.
Included documentation may vary according to platform and packager. All
documentation is posted on http://www.privoxy.org, in case you don't have it,
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.
+help to 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
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).
+ 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).
+ * 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.
* 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).
+ 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
+ * 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
* 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.
+The appendix of the Privoxy User Manual also has helpful information on
+understanding actions, and action debugging.
-------------------------------------------------------------------------------
projects / privoxy.git / blobdiff