X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=config;h=4e532aa906276e67a7e0fa8e01186b42decb1963;hp=b561a627b1954cfd15ef2d3b2f7c0bce0c2bcbbf;hb=ed2423c402fdaada57ae8c397a794f66009f0762;hpb=06f39981f918732549d9c21787dffd9587b8d08e diff --git a/config b/config index b561a627..4e532aa9 100644 --- a/config +++ b/config @@ -1,8 +1,8 @@ -# Sample Configuration File for Privoxy v3.0.14 beta +# Sample Configuration File for Privoxy v3.0.19 # -# $Id: config,v 1.80 2009/06/12 14:34:10 fabiankeil Exp $ +# $Id: config,v 1.97 2011/11/19 15:20:23 fabiankeil Exp $ # -# Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/ +# Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/ # #################################################################### # # @@ -113,7 +113,6 @@ # # 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: # http://config.privoxy.org/user-manual/ (or the shortcut: @@ -124,7 +123,6 @@ # # user-manual http://example.com/privoxy/user-manual/ # -# # WARNING!!! # # If set, this option should be the first option in the config @@ -416,7 +414,7 @@ actionsfile user.action # User customizations # separate file, such as user.filter. # filterfile default.filter -#filterfile user.filter # User customizations +filterfile user.filter # User customizations # # # 2.6. logfile @@ -560,7 +558,7 @@ logfile logfile # debug 2 # show each connection status # debug 4 # show I/O status # debug 8 # show header parsing -# debug 16 # log all data written to the network into the logfile +# debug 16 # log all data written to the network # debug 32 # debug force feature # debug 64 # debug regular expression filters # debug 128 # debug redirects @@ -570,6 +568,7 @@ logfile logfile # debug 2048 # CGI user interface # debug 4096 # Startup banner and warnings. # debug 8192 # Non-fatal errors +# debug 32768 # log all data read from the network # # # To select multiple debug levels, you can either add them or @@ -682,13 +681,15 @@ logfile logfile # # Specifies: # -# The IP address and TCP port on which Privoxy will listen for +# The address and TCP port on which Privoxy will listen for # client requests. # # Type of value: # # [IP-Address]:Port # +# [Hostname]:Port +# # Default value: # # 127.0.0.1:8118 @@ -708,20 +709,56 @@ 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. # -# IPv6 addresses containing colons have to be quoted by brackets. +# You can use this statement multiple times to make Privoxy listen +# on more ports or more IP addresses. Suitable if your operating +# system does not support sharing IPv6 and IPv4 protocols on the +# same socket. +# +# If a hostname is used instead of an IP address, Privoxy will +# try to resolve it to an IP address and if there are multiple, +# use the first one returned. +# +# If the address for the hostname isn't already known on the +# system (for example because it's in /etc/hostname), this may +# result in DNS traffic. +# +# If the specified address isn't available on the system, or if +# the hostname can't be resolved, Privoxy will fail to start. +# +# IPv6 addresses containing colons have to be quoted by +# brackets. They can only be used if Privoxy has been compiled +# with IPv6 support. If you aren't sure if your version supports +# it, have a look at http://config.privoxy.org/ show-status. +# +# Some operating systems will prefer IPv6 to IPv4 addresses even if +# the system has no IPv6 connectivity which is usually not expected +# by the user. Some even rely on DNS to resolve localhost which +# mean the "localhost" address used may not actually be local. # -# If you leave out the IP address, Privoxy will bind to all IPv4 +# It is therefore recommended to explicitly configure the intended +# IP address instead of relying on the operating system, unless +# there's a strong reason not to. +# +# If you leave out the 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. 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. +# from the Internet and/ or the local network. Be aware that +# some GNU/Linux distributions modify that behaviour without +# updating the documentation. Check for non-standard patches if +# your Privoxyversion behaves differently. +# +# If you configure Privoxyto be reachable from the network, +# consider using access control lists (ACL's, see below), and/or +# a firewall. # # If you open Privoxy to untrusted users, you will also # want to make sure that the following actions are disabled: # enable-edit-actions and enable-remote-toggle # +# With the exception noted above, listening on multiple addresses +# is currently not supported by Privoxy directly. It can be done +# on most operating systems by letting a packet filter redirect +# request for certain addresses to Privoxy, though. +# # Example: # # Suppose you are running Privoxy on a machine which has the @@ -731,13 +768,11 @@ 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 # # @@ -1010,10 +1045,10 @@ 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 +# Some systems allow IPv4 clients to connect to IPv6 server +# sockets. Then the client's IPv4 address will be translated by the # system into IPv6 address space with special prefix ::ffff:0:0/96 -# (so called IPv4 mapped IPv6 address). Privoxy can handle it +# (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 @@ -1173,7 +1208,7 @@ buffer-limit 4096 # # Parent proxy specified by an IPv6 address: # -# foward / [2001:DB8::1]:8000 +# forward / [2001:DB8::1]:8000 # # # Suppose your parent proxy doesn't support IPv6: @@ -1280,7 +1315,6 @@ buffer-limit 4096 # # # -# # 5.3. forwarded-connect-retries # =============================== # @@ -1321,6 +1355,9 @@ buffer-limit 4096 # manually. Start with a small value and check Privoxy's logfile # from time to time, to see how many retries are usually needed. # +# Due to a bug, this option currently also causes Privoxy to +# retry in case of certain problems with direct connections. +# # Examples: # # forwarded-connect-retries 1 @@ -1485,14 +1522,80 @@ split-large-forms 0 # This option has no effect if Privoxy has been compiled without # keep-alive support. # +# Note that a timeout of five seconds as used in the default +# configuration file significantly decreases the number of +# connections that will be reused. The value is used because some +# browsers limit the number of connections they open to a single +# host and apply the same limit to proxies. This can result in a +# single website "grabbing" all the connections the browser allows, +# which means connections to other websites can't be opened until +# the connections currently in use time out. +# +# Several users have reported this as a Privoxy bug, so the default +# value has been reduced. Consider increasing it to 300 seconds +# or even more if you think your browser can handle it. If your +# browser appears to be hanging it can't. +# # Examples: # # keep-alive-timeout 300 # -keep-alive-timeout 300 +keep-alive-timeout 5 +# +# +# 6.5. default-server-timeout +# ============================ +# +# Specifies: +# +# Assumed server-side keep-alive timeout if not specified by +# the server. +# +# Type of value: +# +# Time in seconds. +# +# Default value: +# +# None +# +# Effect if unset: +# +# Connections for which the server didn't specify the keep-alive +# timeout are not reused. +# +# Notes: +# +# Enabling this option significantly increases the number of +# connections that are reused, provided the keep-alive-timeout +# option is also enabled. # +# While it also increases the number of connections problems when +# Privoxy tries to reuse a connection that already has been closed +# on the server side, or is closed while Privoxy is trying to +# reuse it, this should only be a problem if it happens for the +# first request sent by the client. If it happens for requests +# on reused client connections, Privoxy will simply close the +# connection and the client is supposed to retry the request +# without bothering the user. +# +# Enabling this option is therefore only recommended if the +# connection-sharing option is disabled. +# +# It is an error to specify a value larger than the +# keep-alive-timeout value. +# +# This option has no effect if Privoxy has been compiled without +# keep-alive support. +# +# Examples: # -# 6.5. connection-sharing +# default-server-timeout 60 +# +#default-server-timeout 60 +# +# +# 6.6. connection-sharing # ======================== # # Specifies: @@ -1563,7 +1666,7 @@ keep-alive-timeout 300 #connection-sharing 1 # # -# 6.6. socket-timeout +# 6.7. socket-timeout # ==================== # # Specifies: @@ -1596,7 +1699,7 @@ keep-alive-timeout 300 socket-timeout 300 # # -# 6.7. max-client-connections +# 6.8. max-client-connections # ============================ # # Specifies: @@ -1650,6 +1753,130 @@ socket-timeout 300 # max-client-connections 256 # #max-client-connections 256 + +# +# 6.9. handle-as-empty-doc-returns-ok +# ==================================== +# +# Specifies: +# +# The status code Privoxy returns for pages blocked with +# +handle-as-empty-document. +# +# Type of value: +# +# 0 or 1 +# +# Default value: +# +# 0 +# +# Effect if unset: +# +# Privoxy returns a status 403(forbidden) for all blocked pages. +# +# Effect if set: +# +# Privoxy returns a status 200(OK) for pages blocked with +# +handle-as-empty-document and a status 403(Forbidden) for all +# other blocked pages. +# +# Notes: +# +# This is 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) +# As the bug has been fixed for quite some time this option +# should no longer be needed and will be removed in a future +# release. Please speak up if you have a reason why the option +# should be kept around. +# +#handle-as-empty-doc-returns-ok 1 +# +# +# 1.6.10. enable-compression +# +# Specifies: +# +# Whether or not buffered content is compressed before delivery. +# +# Type of value: +# +# 0 or 1 +# +# Default value: +# +# 0 +# +# Effect if unset: +# +# Privoxy does not compress buffered content. +# +# Effect if set: +# +# Privoxy compresses buffered content before delivering it to +# the client, provided the client supports it. +# +# Notes: +# +# This directive is only supported if Privoxy has been compiled +# with FEATURE_COMPRESSION, which should not to be confused +# with FEATURE_ZLIB. +# +# Compressing buffered content is mainly useful if Privoxy and the +# client are running on different systems. If they are running on +# the same system, enabling compression is likely to slow things +# down. If you didn't measure otherwise, you should assume that +# it does and keep this option disabled. +# +# Privoxy will not compress buffered content below a certain +# length. +# +#enable-compression 1 +# +# +# 1.6.11. compression-level +# +# Specifies: +# +# The compression level that is passed to the zlib library when +# compressing buffered content. +# +# Type of value: +# +# Positive number ranging from 0 to 9. +# +# Default value: +# +# 1 +# +# Notes: +# +# Compressing the data more takes usually longer than compressing +# it less or not compressing it at all. Which level is best +# depends on the connection between Privoxy and the client. If +# you can't be bothered to benchmark it for yourself, you should +# stick with the default and keep compression disabled. +# +# If compression is disabled, the compression level is irrelevant. +# +# 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 +# +# +#compression-level 1 # # # 7. WINDOWS GUI OPTIONS