X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=config;h=7dcb29673ca3996cfbd1d058e3d675df3beab11b;hp=9366b591d799b90d5804461a4abecd7bdf9eb180;hb=56d86bc6052f0ed6a027d54dfcb1e9d7db44627e;hpb=da1d1d9434d42d2a5fef36216bfa77c9e54b765c

diff --git a/config b/config
index 9366b591..7dcb2967 100644
--- a/config
+++ b/config
@@ -1,6 +1,6 @@
-#        Sample Configuration File for Privoxy v3.0.13
+#    Sample Configuration File for Privoxy v3.0.16
 #
-#  $Id: config,v 1.79 2009/05/10 10:21:13 fabiankeil Exp $
+#  $Id: config,v 1.83 2009/11/29 15:04:51 fabiankeil Exp $
 #
 #  Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
 #
@@ -713,10 +713,7 @@ logfile logfile
 #      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. 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.
+#      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:
@@ -1492,7 +1489,58 @@ split-large-forms 0
 keep-alive-timeout 300
 #
 #
-#  6.5. connection-sharing
+#  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:
+#
+#      default-server-timeout 60
+#
+#default-server-timeout 60
+#
+#  6.6. connection-sharing
 #  ========================
 #
 #  Specifies:
@@ -1563,7 +1611,7 @@ keep-alive-timeout 300
 #connection-sharing 1
 #
 #
-#  6.6. socket-timeout
+#  6.7. socket-timeout
 #  ====================
 #
 #  Specifies:
@@ -1596,7 +1644,7 @@ keep-alive-timeout 300
 socket-timeout 300
 #
 #
-#  6.7. max-client-connections
+#  6.8. max-client-connections
 #  ============================
 #
 #  Specifies: