From: hal9 Date: Fri, 9 Nov 2007 11:54:19 +0000 (+0000) Subject: Updated, mostly the new config stuff. X-Git-Tag: v_3_0_7~80 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=feb05ddd5c5703b273a92badb714ecc74e31c833 Updated, mostly the new config stuff. --- diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index f9fd3383..09b7230a 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -259,7 +259,7 @@ CLASS="FILENAME" >

8.1. Finding the Right Mix

8.2. How to Edit

http://config.privoxy.org/show-status. - The editor allows both fine-grained control over every single feature on a - per-URL basis, and easy choosing from wholesale sets of defaults like - enale-edit-actions must be enabled for + this to work. The editor allows both fine-grained control over every single + feature on a per-URL basis, and easy choosing from wholesale sets of defaults + like "Cautious", "Medium" or or + "Advanced". - Warning: the . Warning: the "Advanced" setting is more aggressive, and - will be more likely to cause problems for some sites. Experienced users only!

setting is more + aggressive, and will be more likely to cause problems for some sites. + Experienced users only! +

If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files with your favorite text editor. Look at @@ -887,7 +893,7 @@ CLASS="SECT3" >

8.4.1. The Domain Pattern

8.4.2. The Path Pattern

# Tag every request with the declared content type
-{+client-header-filter{content-type}}
+{+client-header-tagger{content-type}}
 /

8.5.39. Summary

8.7.1. default.action

8.7.2. user.action

14.2. Privoxy's Internal Pages

Short cuts. Turn off, then on:

The User Manual is then available to anyone with access to the proxy, by - following the built-in URL: The User Manual is then available to anyone with access to + Privoxy, by following the built-in URL: + http://config.privoxy.org/user-manual/ @@ -411,7 +415,10 @@ CLASS="VARIABLELIST" >Specifies:

An email address to reach the proxy administrator. +> An email address to reach the Privoxy administrator.

Privoxy's original templates are usually overwritten with each update. Use this option to relocate customized templates - that should be kept. Note that you might be missing new features - if you use outdated templates. + that should be kept. Note that template variables might change + between updates and templates are not guaranteed to work with + Privoxy releases other than the one + they were part of.

regular expressions. These rules permit powerful changes on the content of Web pages, and optionally the headers - as well, e.g., you could disable your favorite JavaScript annoyances, + as well, e.g., you could try to disable your favorite JavaScript annoyances, re-write the actual displayed text, or just have some fun playing buzzword bingo with web pages.

Effect if unset:

No log file is used, all log messages go to the console ( Logging is disabled unless STDERR). +>--no-daemon mode is used.

Privoxy (e.g., it's not blocking an ad you - think it should block) but in most cases you probably will never look at - it. For this reason, it is disabled by default. For troubleshooting - purposes, you will have to explicitly enable it. + think it should block) and it can help you to monitor what your browser + is doing. +

Many users will never look at it, however, and it's a privacy risk + if third parties can get access to it. It is therefore disabled by + default in Privoxy 3.0.7 and later. +

For troubleshooting purposes, you will have to explicitly enable it. + Please don't file any support requests without trying to reproduce + the problem with logging enabled first. Once you read the log messages, + you may even be able to solve the problem on your own.

Your logfile will grow indefinitely, and you will probably want to @@ -1103,23 +1128,11 @@ CLASS="COMMAND" > script has been included.

On SuSE Linux systems, you can place a line like "/var/log/privoxy.* - +1024k 644 nobody.nogroup" in /etc/logfiles, with - the effect that cron.daily will automatically archive, gzip, and empty the - log, when it exceeds 1M size. -

Any log files must be writable by whatever user Privoxy - is being run as (default on UNIX, user id is "privoxy"). @@ -1190,7 +1203,10 @@ CLASS="EMPHASIS"

If debug 8 (show header parsing) is enabled, cookies are - written to the logfile with the rest of the headers. + also written to the logfile with the rest of the headers. + Therefore this option isn't very useful and may be removed + in future releases. Please report to the developers if you + are still using it.

Notes:

This option is only there for debug purposes and you should never +> This option is only there for debugging purposes and you should never need to use it. Privoxy to untrusted users, you will - also want to turn off the enable-remote-toggle - options!

"toggled off" mode, i.e. mostly behave like a normal, - content-neutral proxy where all ad blocking, filtering, etc are disabled. See - enable-remote-toggle below. This is not really useful - anymore, since toggling is much easier via the web interface than via - editing the conf file. +> below.

The windows version will only display the toggle icon in the system tray @@ -1855,8 +1861,7 @@ TARGET="_top" CLASS="APPLICATION" >Privoxy mostly acts like a normal, - content-neutral proxy, i.e. it acts as if none of the actions applied to - any URL. + content-neutral proxy, i.e. doesn't block ads or filter content.

Access to the toggle feature can not recommended - for multi-user environments with untrusted users. Because of - the obvious security implications, this feature is off by default. - Note that malicious client side code (e.g JavaScript) is also potentially - capable of changing

Note that malicious client side code (e.g Java) is also + capable of using this option. +

As a lot of Privoxy's intended - behavior. +>Privoxy users don't read + documentation, this feature has been disabled by default.

Note that you must have compiled Privoxy in a environment with trusted clients, you may enable this feature at your discretion. Note that malicious client - side code (e.g JavaScript) is also potentially capable of changing - Privoxy's intended behavior. + side code (e.g Java) is also capable of using this feature. +

This option may be removed in future releases as it has been obsoleted + by the more general header taggers.

listen-address above) can - modify its configuration for all users. This option is

This option is not - recommendednot recommended for multi-user environments with untrusted users - and is therefore disabled by default. Note that malicious client side code - (e.g JavaScript) is also potentially capable of changing - for environments + with untrusted users and is therefore disabled by default. +

Note that malicious client side code (e.g Java) is also + capable of using the actions editor and you shouldn't enable + this options unless you understand the consequences and are + sure your browser is configured correctly. +

As a lot of Privoxy's intended behavior. +>Privoxy users don't read + documentation, this feature has been disabled by default.

Note that you must have compiled 

  forward-socks4   /               127.0.0.1:9050 .
forward-socks4a / 127.0.0.1:9050 . The public Tor network can't be used to reach your local network, - therefore it's a good idea to make some exceptions: +> network can't be used to + reach your local network, if you need to access local servers you + therefore might want to make some exceptions:

Unencrypted connections to systems in these address ranges will be as (un)secure as the local network is, but the alternative is that you - can't reach the network at all. + can't reach the local network through Privoxy + at all.

If you also want to be able to reach servers in your local network by @@ -3284,7 +3308,7 @@ CLASS="QUOTE" that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.

Only use this option, if you are getting many forwarding related error messages, +> Only use this option, if you are getting lots of forwarding-related error messages that go away when you try again manually. Start with a small value and check Privoxy's logfile from time to time, to see how many retries are usually needed.

6.1. Controlling Privoxy with Your Web Browser

    Privoxy Menu

12.1. License

9.1. Filter File Tutorial


$Id: user-manual.sgml,v 2.38 2007/09/22 16:01:42 fabiankeil Exp $

$Id: user-manual.sgml,v 2.39 2007/11/05 02:34:49 hal9 Exp $

6.1. Controlling Privoxy with Your Web Browser
8.1. Finding the Right Mix
8.2. How to Edit
8.4.1. The Domain Pattern
8.4.2. The Path Pattern
8.5.39. Summary
8.7.1. default.action
8.7.2. user.action
9.1. Filter File Tutorial
12.1. License
14.2. Privoxy's Internal Pages

  • See the full documentation on - fast-redirects - 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. -

  • - What constitutes a "default" configuration has changed, - and you may want to review which actions are "on" by - default. This is primarily a matter of emphasis, but some features - you may have been used to, may now be "off" by default. - There are also a number of new actions and filters you may want to - consider, most of which are not fully incorporated into the default - settings as yet (see above). -

  • 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). -

    standard.action now only includes the enabled actions. + Not all actions as before. +

  • 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. -

    Logging is off by default now. If you need logging, it can be turned on + in the config file. +

  • - Some installers may not automatically start - Privoxy after installation. -

    Three other config file settings are now off by default: + enable-remote-toggle, + enable-remote-http-toggle, + and enable-edit-actions. + If you use or want these, you will need to explicitly enable them, and + be aware of the security issues involved. +