X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Ffaq%2Fconfiguration.html;h=0c0f7a842451ed3d7930da24d779fb2ea153a8c6;hb=c07b987d0ff476c26500a0641baa0b8a42ce19de;hp=f436199df90997a0794bd593ea66c8cfcff9ce72;hpb=3239e60560e2c55a06477816cdcc1dd30c0f4e72;p=privoxy.git diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html index f436199d..0c0f7a84 100644 --- a/doc/webserver/faq/configuration.html +++ b/doc/webserver/faq/configuration.html @@ -17,7 +17,10 @@ TITLE="Miscellaneous" HREF="misc.html">
Based on your feedback and the continuing development, updates of - Based on your feedback and the continuing development, updates of + default.action will be - made available from time to time on the files sectionsubscribe - to our announce mailing list, ijbswa-announce@lists.sourceforge.net.
Note that in the default configuration, only local users (i.e. those on - "localhost") can connect to As of Privoxy, - so this is (normally) not a security problem. +> 3.0.7 these options are disabled by default.
There are a number of pre-defined filters to deal with common annoyances. The filters are only defined here, to invoke them, you need to use the filter action in one of the actions files. Filtering is automatically - disabled for inappropriate MIME types.
in one of the actions files. Content filtering is automatically + disabled for inappropriate MIME types, but if you now better than Privoxy + what should or should not be filtered you can filter any content you like.Filters should + not be confused with blocks, which + is a completely different action, and is more typically used to block ads and + unwanted sites.
If you are familiar with regular expressions, and HTML, you can look at the provided web-based actions file editor
. + Note that the custom actions editor must be explicitly enabled in + the main config file (see enable-edit-actions).If you intend to develop your own filters, you might want to have a look at + Privoxy-Filter-Test.
Please refer to your packet filter's documentation to learn how to intercept and redirect traffic into Privoxy. Afterward you just have - to configure . + Afterward you just have to configure Privoxy to accept intercepted requestsaccept + intercepted requests.
A more interesting approach is Another approach is Privoxy's @@ -1440,9 +1480,9 @@ CLASS="QUOTE" >. See the User Manual TrustTrust documentation - documentation.
These are fairly simple approaches and are not completely foolproof. There are various other configuration options that should be disabled (described @@ -1452,7 +1492,7 @@ TARGET="_top" >the User Manual) so that users can't modify their own configuration and easily circumvent the - whitelist.
Be forewarned that the default templates are subject to being overwritten + during upgrades. You can, however, create completely new templates, + place them in another directory and specify the alternate path in the main + config. For details, have a look at the templdir option.
There is more than one way to do it.
There is more than one way to do it (although Perl is not involved).Editing the BLOCKED template page (see above) may dissuade some users, but this method is easily circumvented. Where you need this level of control, you - should build Privoxy from source, and enable various features that are +> from source, and disable various features that are available as compile-time options. You should does not allow easy bypassing of blocked sites, or changing the current configuration via any connected user's web browser.
Note that all of these features can also be toggled on/off via options in +> Finally, all of these features can also be toggled on/off via options in Privoxy's