-# Sample Configuration File for Privoxy v3.0.11
+# Sample Configuration File for Privoxy v3.0.12
#
-# $Id: p-config.sgml,v 2.36 2009/01/23 14:06:07 fabiankeil Exp $
+# $Id: config,v 1.75 2009/03/21 11:35:37 hal9 Exp $
#
# Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
#
#
# Default value:
#
-# Two example URLs are provided
+# Unset
#
# Effect if unset:
#
# 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
# 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
#
# Effect if unset:
#
-# A default value of 180 seconds is used.
+# 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 180
+# socket-timeout 300
#
-socket-timeout 180
+socket-timeout 300
#
#
# 6. WINDOWS GUI OPTIONS