-# Sample Configuration File for Privoxy v3.0.20
+# Sample Configuration File for Privoxy 3.0.22
#
-# $Id: config,v 1.101 2013/01/09 15:19:47 fabiankeil Exp $
+# $Id: p-config.sgml,v 2.104 2014/05/05 09:59:30 fabiankeil Exp $
#
-# Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
+# Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/
#
####################################################################
# #
# 3. DEBUGGING #
# 4. ACCESS CONTROL AND SECURITY #
# 5. FORWARDING #
-# 6. WINDOWS GUI OPTIONS #
+# 6. MISCELLANEOUS #
+# 7. WINDOWS GUI OPTIONS #
# #
####################################################################
#
#
#templdir .
#
-# 2.3. logdir
+# 2.3. temporary-directory
+# =========================
+#
+# Specifies:
+#
+# A directory where Privoxy can create temporary files.
+#
+# Type of value:
+#
+# Path name
+#
+# Default value:
+#
+# unset
+#
+# Effect if unset:
+#
+# No temporary files are created, external filters don't work.
+#
+# Notes:
+#
+# To execute external filters, Privoxy has to create temporary
+# files. This directive specifies the directory the temporary
+# files should be written to.
+#
+# It should be a directory only Privoxy (and trusted users) can
+# access.
+#
+#temporary-directory .
+#
+# 2.4. logdir
# ============
#
# Specifies:
#
logdir .
#
-# 2.4. actionsfile
+# 2.5. actionsfile
# =================
#
# Specifies:
actionsfile default.action # Main actions file
actionsfile user.action # User customizations
#
-# 2.5. filterfile
+# 2.6. filterfile
# ================
#
# Specifies:
filterfile default.filter
filterfile user.filter # User customizations
#
-# 2.6. logfile
+# 2.7. logfile
# =============
#
# Specifies:
#
logfile logfile
#
-# 2.7. trustfile
+# 2.8. trustfile
# ===============
#
# Specifies:
#
# Type of value:
#
-# None
+# 1 or 0
#
# Default value:
#
-# Unset
+# 0
#
# Effect if unset:
#
# This option is only there for debugging purposes. It will
# drastically reduce performance.
#
-#single-threaded
+#single-threaded 1
#
# 3.3. hostname
# ==============
#
buffer-limit 4096
#
+# 4.9. enable-proxy-authentication-forwarding
+# ============================================
+#
+# Specifies:
+#
+# Whether or not proxy authentication through Privoxy should
+# work.
+#
+# Type of value:
+#
+# 0 or 1
+#
+# Default value:
+#
+# 0
+#
+# Effect if unset:
+#
+# Proxy authentication headers are removed.
+#
+# Notes:
+#
+# Privoxy itself does not support proxy authentication, but can
+# allow clients to authenticate against Privoxy's parent proxy.
+#
+# By default Privoxy (3.0.21 and later) don't do that and remove
+# Proxy-Authorization headers in requests and Proxy-Authenticate
+# headers in responses to make it harder for malicious sites to
+# trick inexperienced users into providing login information.
+#
+# If this option is enabled the headers are forwarded.
+#
+# Enabling this option is not recommended if there is no parent
+# proxy that requires authentication or if the local network
+# between Privoxy and the parent proxy isn't trustworthy. If
+# proxy authentication is only required for some requests, it is
+# recommended to use a client header filter to remove the
+# authentication headers for requests where they aren't needed.
+#
+enable-proxy-authentication-forwarding 0
+#
# 5. FORWARDING
# ==============
#
# To chain Privoxy and Tor, both running on the same system, you
# would use something like:
#
-# forward-socks5 / 127.0.0.1:9050 .
+# forward-socks5t / 127.0.0.1:9050 .
#
# The public Tor network can't be used to reach your local
# network, if you need to access local servers you therefore
# Privoxy, enable this option and configure your packet filter
# to redirect outgoing HTTP connections into Privoxy.
#
+# Note that intercepting encrypted connections (HTTPS) isn't
+# supported.
+#
# Make sure that Privoxy's own requests aren't redirected as
# well. Additionally take care that Privoxy can't intentionally
# connect to itself, otherwise you could run into redirection
#
# Default value:
#
-# None
+# 128
#
# Effect if unset:
#
# Obviously using this option only makes sense if you choose a
# limit below the one enforced by the operating system.
#
+# One most POSIX-compliant systems Privoxy can't properly deal
+# with more than FD_SETSIZE file descriptors at the same time
+# and has to reject connections if the limit is reached. This
+# will likely change in a future version, but currently this
+# limit can't be increased without recompiling Privoxy with a
+# different FD_SETSIZE limit.
+#
# Examples:
#
# max-client-connections 256