There are many improvements and new features in There are many improvements and new features since Privoxy 3.0.4 - :
Privoxy 3.0.6, the last stable release:
Mulitiple filter files can now be specifed in config. This allows for - locally defined filters that can be maintained separately from the filters as - supplied by the developers. -
- There are a number of new actions: -
redirect -
In addition, fast-redirects - has been significantly improved with enhanced syntax. -
And hide-referrer Header filtering can be done with dedicated header filters now. As a result + the actions "filter-client-headers" and "filter-server-headers" - has a new option, conditional block. -
MS-Windows versions can now be installed and - started as a service. -
In addition, there are various bug fixes and significant enhancements, including - error pages are no longer cached, better DNS error handling, and various logging - improvements. +>Privoxy 3.0.5 to apply + the content filters to the headers as, well have been removed again.
+ On the other hand, other installers may not overwrite any existing configuration + files, thinking you will want to do that. You may want to manually check + your saved files against the newer versions to see if the improvements have + merit, or whether there are new options that you may want to consider. + There are a number of new features, but most won't be available unless + these features are incorporated into your configuration somehow. +
See the full documentation on fast-redirects - which has changed syntax, and may require adjustments to local configs. + which has changed syntax, and will require adjustments to local configs, + such as user.action. You must reference the new + syntax:
{ +fast-redirects{check-decoded-url} }
+ .example.com
+ mybank.com
+ .google. |
The jarfile, cookie logger, is off by default now. +>, + cookie logger, is off by default now.
The default actions setting is now Cautious. Previous + releases had a default setting of Medium. Experienced + users may want to adjust this, as it is fairly conservative by Privoxy + standards and past practices. See http://config.privoxy.org/edit-actions-list?f=default. New users + should try the default settings for a while before turning up the volume. +
The default setting has filtering turned off, which + subsequently means that compression is on. Remember + that filtering does not work on compressed pages, so if you use, or want to + use, filtering, you will need to force compression off. Example: +
{ +filter{google} +prevent-compression }
+ .google. |
Or if you use a number of filters, or filter many sites, you may just want + to turn off compression for all sites in + default.action (or + user.action). +
Also, session-cookies-only is + off by default now. If you've liked this feature in the past, you may want + to turn it back on in user.action now.