There are very significant changes from older versions of +> There are very significant changes from earlier Junkbuster to the current +> versions to the current Privoxy. Configuration is substantially - changed. . The number, names, syntax, and + purposes of configuration files have substantially changed. + Junkbuster 2.0.x and earlier - configuration files will not migrate. The functionality of the old - configuration + files will not migrate, Junkbuster 2.9.x + and Privoxy configurations will need to be + ported. The functionalities of the old blockfile, , + cookiefile and - and imagelist, are now combined into the - + are now combined into the "actions files". "actions + files". + default.action, - is the main actions file. Local exceptions should best be put into - , is the main actions file. Local + exceptions should best be put into user.action.
A A "filter file" (typically (typically + default.filter) - is new as of ) is new as of Privoxy 2.9.x, and provides some - of the new sophistication (explained below). Privoxy + 2.9.x, and provides some of the new sophistication (explained + below). config is - much the same as before.
is much the same as before.If upgrading from a 2.0.x version, you will have to use the new config files, and possibly adapt any personal rules from your older files. @@ -182,17 +196,17 @@ CLASS="APPLICATION" >
The primary configuration file for cookie management, ad and banner +> The primary configuration files for cookie management, ad and banner blocking, and many other aspects of Privoxy - configuration is in the "actions" files. It is strongly - recommended to become familiar with the new actions concept below, - before modifying these files. Locally defined rules + configuration are the actions + files. It is strongly recommended to become familiar with the new + actions concept below, before modifying these files. Locally defined rules should go into user.action