X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fconfiguration.html;h=8460cb1e0aa3c46d215a932ba61085a9bf87d3f9;hb=c83713758e9465e03ec3b0228c433e6f2d843352;hp=0dc23c0d94e5c09801a6f889e193a277507ace23;hpb=6231ae15da15f2db745a7dd1bccc672b2394f7cb;p=privoxy.git diff --git a/doc/webserver/user-manual/configuration.html b/doc/webserver/user-manual/configuration.html index 0dc23c0d..8460cb1e 100644 --- a/doc/webserver/user-manual/configuration.html +++ b/doc/webserver/user-manual/configuration.html @@ -4,7 +4,7 @@ Privoxy Configuration - + @@ -15,7 +15,7 @@
- + @@ -40,7 +40,7 @@
Privoxy 3.0.27 User ManualPrivoxy 3.0.29 User Manual
Prev
-

    Privoxy Menu

+

    Privoxy Menu


@@ -51,7 +51,8 @@ + "http://config.privoxy.org/client-tags" target="_top">View or toggle the tags that can be set based + on the client's address + "https://www.privoxy.org/3.0.29/user-manual/" target="_top">Documentation
        ▪  View the source code version numbers
        ▪  
        ▪  Documentation
@@ -92,15 +93,15 @@

6.2. Configuration Files Overview

For Unix, *BSD and GNU/Linux, all configuration files are located in /etc/privoxy/ - by default. For MS Windows and OS/2 these are all in the same directory as the Privoxy executable.

+ by default. For MS Windows these are all in the same directory as the Privoxy + executable. The name and number of configuration files has changed from previous versions, and is subject to + change as development progresses.

The installed defaults provide a reasonable starting point, though some settings may be aggressive by some standards. For the time being, the principle configuration files are:

  • The main configuration file is named config on - GNU/Linux, Unix, BSD, and OS/2, and config.txt on Windows. This is a required - file.

    + GNU/Linux, Unix, BSD, and config.txt on Windows. This is a required file.

  • match-all.action is used to define which "actions" @@ -145,6 +146,9 @@ listening address of Privoxy, these "wake up" requests must obviously be sent to the old listening address.

    +

    While under development, the configuration content is subject to change. The below documentation may not be + accurate by the time you read this. Also, what constitutes a "default" setting, may + change, so please check all your configuration files on important issues.