-# Sample Configuration File for Privoxy v3.0.11
+# Sample Configuration File for Privoxy v3.0.12
#
-# $Id: config,v 1.67 2008/08/30 15:31:53 fabiankeil Exp $
+# $Id: config,v 1.74 2009/02/19 17:26:26 fabiankeil Exp $
#
-# Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
+# Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
#
####################################################################
# #
# If set, this option should be the first option in the config
# file, because it is used while the config file is being read.
#
-#user-manual http://www.privoxy.org/user-manual/
+user-manual /home/halb/privoxy/share/doc/privoxy/user-manual/
#
#
# 1.2. trust-info-url
#
# 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
#
# No trailing "/", please.
#
-confdir .
+confdir /home/halb/privoxy/etc
#
#
# 2.2. templdir
#
# No trailing "/", please.
#
-logdir .
+logdir /home/halb/privoxy/var/log/privoxy
#
#
# 2.4. actionsfile
#
# 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:
#
# 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,
# 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
#
#
# 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
# 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
# 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
#
# 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
# =======================
#
projects / privoxy.git / blobdiff