X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=ba974539df0f024aa0f5ff820acf2c48fbdb9e14;hp=d509c42ffd850b344bbd9cff7836dee92566a9f6;hb=3f47e92cd5ade006b4911f98d0f24e61048075e6;hpb=65e01393b77af2ab94844cb13efb3d5e321f1254 diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index d509c42f..ba974539 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -1,11 +1,9 @@ + +I. INTRODUCTION + =============== + This file holds Privoxy's main configuration. Privoxy detects @@ -251,30 +240,22 @@ II. FORMAT OF THE CONFIGURATION FILE Unix, in local filesystem (may not work with all browsers): -   user-manual  file:///usr/share/doc/privoxy-&p-version;/user-manual/ - Windows, in local filesystem, must use forward slash notation: -   user-manual  file:/c:/some-dir/privoxy-&p-version;/user-manual/ - Windows, UNC notation (with forward slashes): -   user-manual  file://///some-server/some-path/privoxy-&p-version;/user-manual/ - --> The best all purpose solution is simply to put the full local PATH to where the User Manual is located: - -   user-manual  /usr/share/doc/privoxy/user-manual - + user-manual /usr/share/doc/privoxy/user-manual The User Manual is then available to anyone with access to Privoxy, by following the built-in URL: @@ -285,9 +266,7 @@ II. FORMAT OF THE CONFIGURATION FILE If the documentation is not on the local system, it can be accessed from a remote server, as: - -   user-manual  http://example.com/privoxy/user-manual/ - + user-manual http://example.com/privoxy/user-manual/ @@ -1035,7 +1014,6 @@ actionsfile The available debug levels are: - debug 1 # Log the destination for each request &my-app; let through. See also debug 1024. debug 2 # show each connection status @@ -1054,7 +1032,6 @@ actionsfile debug 32768 # log all data read from the network debug 65536 # Log the applying actions - To select multiple debug levels, you can either add them or use multiple debug lines. @@ -1329,21 +1306,17 @@ actionsfile (192.168.0.0) and has another outside connection with a different address. You want it to serve requests from inside only: - listen-address 192.168.0.1:8118 - Suppose you are running Privoxy on an IPv6-capable machine and you want it to listen on the IPv6 address of the loopback device: - listen-address [::1]:8118 - @@ -1790,49 +1763,39 @@ ACLs: permit-access and deny-access is OK. The absence of a dst_addr implies that all destination addresses are OK: - permit-access localhost - Allow any host on the same class C subnet as www.privoxy.org access to nothing but www.example.com (or other domains hosted on the same system): - permit-access www.privoxy.org/24 www.example.com/32 - Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere, with the exception that 192.168.45.73 may not access the IP address behind www.dirty-stuff.example.com: - permit-access 192.168.45.64/26 deny-access 192.168.45.73 www.dirty-stuff.example.com - Allow access from the IPv4 network 192.0.2.0/24 even if listening on an IPv6 wild card address (not supported on all platforms): - permit-access 192.0.2.0/24 - This is equivalent to the following line even if listening on an IPv4 address (not supported on all platforms): - permit-access [::ffff:192.0.2.0]/120 - @@ -2031,7 +1994,7 @@ ACLs: permit-access and deny-access -@@trusted-cgi-referer http://www.example.org/local-privoxy-control-page]]> +@@#trusted-cgi-referer http://www.example.org/local-privoxy-control-page]]> @@ -2138,40 +2101,32 @@ ACLs: permit-access and deny-access Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle): - forward / parent-proxy.example.org:8080 forward :443 . - Everything goes to our example ISP's caching proxy, except for requests to that ISP's sites: - forward / caching-proxy.isp.example.net:8000 forward .isp.example.net . - Parent proxy specified by an IPv6 address: - forward / [2001:DB8::1]:8000 - Suppose your parent proxy doesn't support IPv6: - forward / parent-proxy.example.org:8000 forward ipv6-server.example.org . forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> . - @@ -2276,30 +2231,24 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to the Internet. - forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080 forward .example.com . - A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this: - forward-socks4 / socks-gw.example.com:1080 . - To chain Privoxy and Tor, both running on the same system, you would use something like: - forward-socks5t / 127.0.0.1:9050 . - Note that if you got Tor through one of the bundles, you may have to change the port from 9050 to 9150 (or even another one). @@ -2311,13 +2260,11 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t reach your local network, if you need to access local servers you therefore might want to make some exceptions: - forward 192.168.*.*/ . - forward 10.*.*.*/ . - forward 127.*.*.*/ . + forward 10.*.*.*/ . + forward 127.*.*.*/ . - Unencrypted connections to systems in these address ranges will be as (un)secure as the local network is, but the alternative is that you @@ -2330,11 +2277,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t using their names, you will need additional exceptions that look like this: - forward localhost/ . - @@ -2362,23 +2307,19 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t host-a: - forward / . forward .isp-b.example.net host-b:8118 - host-b: - forward / . forward .isp-a.example.org host-a:8118 - Now, your users can set their browser's proxy to use either @@ -2397,7 +2338,6 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t run on the same box, your squid configuration could then look like this: - # Define Privoxy as parent proxy (without ICP) cache_peer 127.0.0.1 parent 8118 7 no-query @@ -2410,7 +2350,6 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t # Forward all the rest to Privoxy never_direct allow all - You would then need to change your browser's proxy settings to squid's address and port. @@ -2423,11 +2362,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t say, on antivir.example.com, port 8010: - forward / . forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010 - ]]> @@ -3375,8 +3312,8 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t This directive was added as a work-around for Firefox bug 492459: Websites are no longer rendered if SSL requests for JavaScripts are blocked by a proxy. - (https://bugzilla.mozilla.org/show_bug.cgi?id=492459), + ( + https://bugzilla.mozilla.org/show_bug.cgi?id=492459), the bug has been fixed for quite some time, but this directive is also useful to make it harder for websites to detect whether or not resources are being blocked. @@ -3495,20 +3432,20 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Examples: - # Best speed (compared to the other levels) compression-level 1 + # Best compression compression-level 9 + # No compression. Only useful for testing as the added header # slightly increases the amount of data that has to be sent. # If your benchmark shows that using this compression level # is superior to using no compression at all, the benchmark # is likely to be flawed. compression-level 0 - - + @@ -3656,14 +3593,12 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Examples: - # Define a couple of tags, the described effect requires action sections # that are enabled based on CLIENT-TAG patterns. client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions disable-content-filters Disable content-filters but do not affect other actions - - + @@ -3721,12 +3656,10 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Examples: - # Increase the time to life for temporarily enabled tags to 3 minutes client-tag-lifetime 180 - - + @@ -3795,13 +3728,11 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Examples: - # Allow systems that can reach Privoxy to provide the client # IP address with a X-Forwarded-For header. trust-x-forwarded-for 1 - - + @@ -3870,12 +3801,10 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Examples: - # Increase the receive buffer size receive-buffer-size 32768 - - + @@ -3904,15 +3833,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#activity-animation 1]]> - - activity-animation 1 - - - - + ]]> @@ -3926,15 +3849,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-messages 1]]> - - log-messages 1 - - - - + ]]> @@ -3952,15 +3869,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-buffer-size 1]]> - - log-buffer-size 1 - - - - + ]]> @@ -3972,15 +3883,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-max-lines 200]]> - - log-max-lines 200 - - - - + ]]> @@ -3993,15 +3898,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-highlight-messages 1]]> - - log-highlight-messages 1 - - - - + ]]> @@ -4012,15 +3911,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-font-name Comic Sans MS]]> - - log-font-name Comic Sans MS - - - - + ]]> @@ -4031,15 +3924,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#log-font-size 8]]> - - log-font-size 8 - - - - + ]]> @@ -4052,15 +3939,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#show-on-task-bar 0]]> - - show-on-task-bar 0 - - - - + ]]> @@ -4073,15 +3954,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#close-button-minimizes 1]]> - - close-button-minimizes 1 - - - - + ]]> @@ -4095,15 +3970,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t @@#hide-console]]> - - #hide-console - - - - + ]]>