X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=config;h=e0ea87a4c81d31d3e83680b9b208d0f235012b28;hb=e734bb1389aaa25ccc30da467aa439a9b00f9973;hp=82183aa731b5e24b479b188e98dd59b83d100cdc;hpb=326a140617e76ff5e66df67121da18c932a4f753;p=privoxy.git diff --git a/config b/config index 82183aa7..e0ea87a4 100644 --- a/config +++ b/config @@ -1,8 +1,8 @@ -# Sample Configuration File for Privoxy v3.0.9 +# Sample Configuration File for Privoxy v3.0.13 # -# $Id: p-config.sgml,v 2.30 2008/03/27 18:31:20 fabiankeil Exp $ +# $Id: p-config.sgml,v 2.48 2009/04/17 11:42:07 fabiankeil Exp $ # -# Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/ +# Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/ # #################################################################### # # @@ -147,7 +147,7 @@ # # Default value: # -# Two example URLs are provided +# Unset # # Effect if unset: # @@ -166,8 +166,8 @@ # don't end up locked out from the information on why they were # locked out in the first place! # -trust-info-url http://www.example.com/why_we_block.html -trust-info-url http://www.example.com/what_we_allow.html +#trust-info-url http://www.example.com/why_we_block.html +#trust-info-url http://www.example.com/what_we_allow.html # # # 1.3. admin-address @@ -305,8 +305,8 @@ confdir . # # Specifies: # -# The directory where all logging takes place (i.e. where logfile -# and jarfile are located). +# The directory where all logging takes place (i.e. where the +# logfile is located). # # Type of value: # @@ -340,11 +340,11 @@ logdir . # # Default values: # -# standard.action # Internal purposes, no editing recommended +# match-all.action # Actions that are applied to all sites and maybe overruled later on. # -# default.action # Main actions file +# default.action # Main actions file # -# user.action # User customizations +# user.action # User customizations # # Effect if unset: # @@ -355,10 +355,9 @@ logdir . # Multiple actionsfile lines are permitted, and are in fact # recommended! # -# The default values include standard.action, which is used -# for internal purposes and should be loaded, default.action, -# which is the "main" actions file maintained by the developers, -# and user.action, where you can make your personal additions. +# The default values are default.action, which is the "main" +# actions file maintained by the developers, and user.action, +# where you can make your personal additions. # # Actions files contain all the per site and per URL configuration # for ad blocking, cookie management, privacy considerations, @@ -370,7 +369,7 @@ logdir . # was necessary to be consistent with the other file options and # to allow previously forbidden characters. # -actionsfile standard.action # Internal purpose, recommended +actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on. actionsfile default.action # Main actions file actionsfile user.action # User customizations # @@ -468,40 +467,7 @@ filterfile default.filter logfile logfile # # -# 2.7. jarfile -# ============= -# -# Specifies: -# -# The file to store intercepted cookies in -# -# Type of value: -# -# File name, relative to logdir -# -# Default value: -# -# Unset (commented out). When activated: jarfile (Unix) or -# privoxy.jar (Windows). -# -# Effect if unset: -# -# Intercepted cookies are not stored in a dedicated log file. -# -# Notes: -# -# The jarfile may grow to ridiculous sizes over time. -# -# If debug 8 (show header parsing) is enabled, cookies are 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. -# -#jarfile jarfile -# -# -# 2.8. trustfile +# 2.7. trustfile # =============== # # Specifies: @@ -590,7 +556,7 @@ logfile logfile # # The available debug levels are: # -# debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request) +# debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. # debug 2 # show each connection status # debug 4 # show I/O status # debug 8 # show header parsing @@ -600,7 +566,7 @@ logfile logfile # debug 128 # debug redirects # debug 256 # debug GIF de-animation # debug 512 # Common Log Format -# debug 1024 # Unused +# debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why. # debug 2048 # CGI user interface # debug 4096 # Startup banner and warnings. # debug 8192 # Non-fatal errors @@ -610,9 +576,9 @@ logfile logfile # use multiple debug lines. # # A debug level of 1 is informative because it will show you each -# request as it happens. 1, 4096 and 8192 are recommended so that -# you will notice when things go wrong. The other levels are -# probably only of interest if you are hunting down a specific +# request as it happens. 1, 1024, 4096 and 8192 are recommended +# so that you will notice when things go wrong. The other levels +# are probably only of interest if you are hunting down a specific # problem. They can produce a hell of an output (especially 16). # # Privoxy used to ship with the debug levels recommended above @@ -634,7 +600,8 @@ logfile logfile # you read the log messages, you may even be able to solve the # problem on your own. # -#debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request) +#debug 1 # Log the destination for each request Privoxy let through. +#debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why. #debug 4096 # Startup banner and warnings #debug 8192 # Non-fatal errors # @@ -728,9 +695,9 @@ logfile logfile # # Effect if unset: # -# Bind to 127.0.0.1 (localhost), port 8118. This is suitable and -# recommended for home users who run Privoxy on the same machine -# as their browser. +# Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is suitable +# and recommended for home users who run Privoxy on the same +# machine as their browser. # # Notes: # @@ -741,10 +708,15 @@ logfile logfile # if you want to serve requests from other machines (e.g. on your # local network) as well, you will need to override the default. # -# If you leave out the IP address, Privoxy will bind to all +# IPv6 addresses containing colons have to be quoted by brackets. +# +# If you leave out the IP address, Privoxy will bind to all IPv4 # interfaces (addresses) on your machine and may become reachable # from the Internet. In that case, consider using access control -# lists (ACL's, see below), and/or a firewall. +# lists (ACL's, see below), and/or a firewall. If the hostname +# is localhost, Privoxy will explicitly try to bind to an IPv4 +# address. For other hostnames it depends on the operating system +# which IP version will be used. # # If you open Privoxy to untrusted users, you will also # want to make sure that the following actions are disabled: @@ -760,6 +732,12 @@ logfile logfile # 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 +# +# listen-address 127.0.0.1:8118 # # @@ -975,18 +953,28 @@ enforce-blocks 0 # # Type of value: # -# src_addr[/src_masklen] [dst_addr[/dst_masklen]] +# src_addr[:port][/src_masklen] [dst_addr[:port][/dst_masklen]] +# +# Where src_addr and dst_addr are IPv4 addresses in dotted +# decimal notation or valid DNS names, port is a port number, and +# src_masklen and dst_masklen are subnet masks in CIDR notation, +# i.e. integer values from 2 to 30 representing the length +# (in bits) of the network address. The masks and the whole +# destination part are optional. # -# Where src_addr and dst_addr are IP addresses in dotted decimal -# notation or valid DNS names, and src_masklen and dst_masklen are -# subnet masks in CIDR notation, i.e. integer values from 2 to 30 -# representing the length (in bits) of the network address. The -# masks and the whole destination part are optional. +# If your system implements RFC 3493, then src_addr and dst_addr +# can be IPv6 addresses delimeted by brackets, port can be a +# number or a service name, and src_masklen and dst_masklen can +# be a number from 0 to 128. # # Default value: # # Unset # +# If no port is specified, any port will match. If no src_masklen +# or src_masklen is given, the complete IP address has to match +# (i.e. 32 bits for IPv4 and 128 bits for IPv6). +# # Effect if unset: # # Don't restrict access further than implied by listen-address @@ -1022,6 +1010,12 @@ enforce-blocks 0 # names. If a DNS name resolves to multiple IP addresses, only # the first one is used. # +# Some systems allows IPv4 client to connect to IPv6 server +# socket. Then the client's IPv4 address will be translated by +# system into IPv6 address space with special prefix ::ffff:0:0/96 +# (so called IPv4 mapped IPv6 address). Privoxy can handle it +# and maps such ACL addresses automatically. +# # Denying access to particular sites by ACL may have undesired # side effects if the site in question is hosted on a machine # which also hosts other sites (most sites are). @@ -1049,6 +1043,16 @@ enforce-blocks 0 # 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 # # # 4.8. buffer-limit @@ -1126,7 +1130,7 @@ buffer-limit 4096 # to denote "all URLs". http_parent[:port] is the DNS name or # IP address of the parent HTTP proxy through which the requests # should be forwarded, optionally followed by its listening port -# (default: 8080). Use a single dot (.) to denote "no forwarding". +# (default: 8000). Use a single dot (.) to denote "no forwarding". # # Default value: # @@ -1141,6 +1145,13 @@ buffer-limit 4096 # If http_parent is ".", then requests are not forwarded to # another HTTP proxy but are made directly to the web servers. # +# http_parent can be a numerical IPv6 address (if RFC 3493 is +# implemented). To prevent clashes with the port delimiter, +# the whole IP address has to be put into brackets. On the other +# hand a target_pattern containing an IPv6 address has to be put +# into angle brackets (normal brackets are reserved for regular +# expressions already). +# # Multiple lines are OK, they are checked in sequence, and the # last match wins. # @@ -1160,6 +1171,16 @@ buffer-limit 4096 # forward .isp.example.net . # # +# Parent proxy specified by an IPv6 address: +# +# foward / [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]:*> . # # # 5.2. forward-socks4, forward-socks4a and forward-socks5 @@ -1202,6 +1223,13 @@ buffer-limit 4096 # With forward-socks5 the DNS resolution will happen on the remote # server as well. # +# socks_proxy and http_parent can be a numerical IPv6 address +# (if RFC 3493 is implemented). To prevent clashes with the port +# delimiter, the whole IP address has to be put into brackets. On +# the other hand a target_pattern containing an IPv6 address has +# to be put into angle brackets (normal brackets are reserved +# for regular expressions already). +# # If http_parent is ".", then requests are not forwarded to another # HTTP proxy but are made (HTTP-wise) directly to the web servers, # albeit through a SOCKS proxy. @@ -1226,7 +1254,7 @@ buffer-limit 4096 # To chain Privoxy and Tor, both running on the same system, # you would use something like: # -# forward-socks4a / 127.0.0.1:9050 . +# forward-socks5 / 127.0.0.1:9050 . # # # The public Tor network can't be used to reach your local network, @@ -1419,6 +1447,86 @@ allow-cgi-request-crunching 0 split-large-forms 0 # # +# 5.7. keep-alive-timeout +# ======================== +# +# Specifies: +# +# Number of seconds after which an open connection will no longer +# be reused. +# +# Type of value: +# +# Time in seconds. +# +# Default value: +# +# None +# +# Effect if unset: +# +# Connections are not reused. +# +# Notes: +# +# This option has no effect if Privoxy has been compiled without +# keep-alive support. +# +# Notes: +# +# Note that reusing connections doesn't necessary cause +# speedups. There are also a few privacy implications you should +# be aware of. +# +# Outgoing connections are shared between clients (if there are +# more than one) and closing the client that initiated the outgoing +# connection does not affect the connection between Privoxy and +# the server unless the client's request hasn't been completed +# yet. If the outgoing connection is idle, it will not be closed +# until either Privoxy's or the server's timeout is reached. While +# it's open, the server knows that the system running Privoxy is +# still there. +# +# Examples: +# +# keep-alive-timeout 300 +# +keep-alive-timeout 300 +# +# +# 5.8. socket-timeout +# ==================== +# +# Specifies: +# +# Number of seconds after which a socket times out if no data +# is received. +# +# Type of value: +# +# Time in seconds. +# +# Default value: +# +# None +# +# Effect if unset: +# +# A default value of 300 seconds is used. +# +# Notes: +# +# For SOCKS requests the timeout currently doesn't start until +# the SOCKS server accepted the request. This will be fixed in +# the next release. +# +# Examples: +# +# socket-timeout 300 +# +socket-timeout 300 +# +# # 6. WINDOWS GUI OPTIONS # ======================= #