+#
+# The templates are assumed to be located in confdir/template.
+#
+# Notes:
+#
+# Privoxy's original templates are usually overwritten with each
+# update. Use this option to relocate customized templates that
+# should be kept. As template variables might change between
+# updates, you shouldn't expect templates to work with Privoxy
+# releases other than the one they were part of, though.
+#
+#templdir .
+#
+#
+# 2.3. logdir
+# ============
+#
+# Specifies:
+#
+# The directory where all logging takes place (i.e. where the
+# logfile is located).
+#
+# Type of value:
+#
+# Path name
+#
+# Default value:
+#
+# /var/log/privoxy (Unix) or Privoxy installation dir (Windows)
+#
+# Effect if unset:
+#
+# Mandatory
+#
+# Notes:
+#
+# No trailing "/", please.
+#
+logdir .
+#
+#
+# 2.4. actionsfile
+# =================
+#
+# Specifies:
+#
+# The actions file(s) to use
+#
+# Type of value:
+#
+# Complete file name, relative to confdir
+#
+# Default values:
+#
+# standard.action # Internal purposes, no editing recommended
+#
+# default.action # Main actions file
+#
+# user.action # User customizations
+#
+# Effect if unset:
+#
+# No actions are taken at all. More or less neutral proxying.
+#
+# Notes:
+#
+# 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.
+#
+# Actions files contain all the per site and per URL configuration
+# for ad blocking, cookie management, privacy considerations,
+# etc. There is no point in using Privoxy without at least one
+# actions file.
+#
+# Note that since Privoxy 3.0.7, the complete filename, including
+# the ".action" extension has to be specified. The syntax change
+# was necessary to be consistent with the other file options and
+# to allow previously forbidden characters.
+#
+actionsfile standard.action # Internal purpose, recommended
+actionsfile default.action # Main actions file
+actionsfile user.action # User customizations
+#
+#
+# 2.5. filterfile
+# ================
+#
+# Specifies:
+#
+# The filter file(s) to use
+#
+# Type of value:
+#
+# File name, relative to confdir
+#
+# Default value:
+#
+# default.filter (Unix) or default.filter.txt (Windows)
+#
+# Effect if unset:
+#
+# No textual content filtering takes place, i.e. all +filter{name}
+# actions in the actions files are turned neutral.
+#
+# Notes:
+#
+# Multiple filterfile lines are permitted.
+#
+# The filter files contain content modification rules that use
+# regular expressions. These rules permit powerful changes on the
+# content of Web pages, and optionally the headers as well, e.g.,
+# you could try to disable your favorite JavaScript annoyances,
+# re-write the actual displayed text, or just have some fun
+# playing buzzword bingo with web pages.
+#
+# The +filter{name} actions rely on the relevant filter (name)
+# to be defined in a filter file!
+#
+# A pre-defined filter file called default.filter that contains a
+# number of useful filters for common problems is included in the
+# distribution. See the section on the filter action for a list.
+#
+# It is recommended to place any locally adapted filters into a
+# separate file, such as user.filter.
+#
+filterfile default.filter
+#filterfile user.filter # User customizations
+#
+#
+# 2.6. logfile
+# =============
+#
+# Specifies:
+#
+# The log file to use
+#
+# Type of value:
+#
+# File name, relative to logdir
+#
+# Default value:
+#
+# Unset (commented out). When activated: logfile (Unix) or
+# privoxy.log (Windows).
+#
+# Effect if unset:
+#
+# No logfile is written.
+#
+# Notes:
+#
+# The logfile is where all logging and error messages are
+# written. The level of detail and number of messages are set with
+# the debug option (see below). The logfile can be useful for
+# tracking down a problem with Privoxy (e.g., it's not blocking
+# an ad you think it should block) and it can help you to monitor
+# what your browser is doing.
+#
+# Depending on the debug options below, the logfile may be a
+# privacy risk if third parties can get access to it. As most
+# users will never look at it, Privoxy 3.0.7 and later only log
+# fatal errors by default.
+#
+# For most troubleshooting purposes, you will have to change that,
+# please refer to the debugging section for details.
+#
+# Your logfile will grow indefinitely, and you will probably
+# want to periodically remove it. On Unix systems, you can do
+# this with a cron job (see "man cron"). For Red Hat based Linux
+# distributions, a logrotate script has been included.
+#
+# Any log files must be writable by whatever user Privoxy is
+# being run as (on Unix, default user id is "privoxy").
+#
+logfile logfile
+#
+#
+# 2.7. trustfile
+# ===============
+#
+# Specifies:
+#
+# The name of the trust file to use
+#
+# Type of value:
+#
+# File name, relative to confdir
+#
+# Default value:
+#
+# Unset (commented out). When activated: trust (Unix) or trust.txt
+# (Windows)
+#
+# Effect if unset:
+#
+# The entire trust mechanism is disabled.
+#
+# Notes:
+#
+# The trust mechanism is an experimental feature for building
+# white-lists and should be used with care. It is NOT recommended
+# for the casual user.
+#
+# If you specify a trust file, Privoxy will only allow access to
+# sites that are specified in the trustfile. Sites can be listed
+# in one of two ways:
+#
+# Prepending a ~ character limits access to this site only (and
+# any sub-paths within this site), e.g. ~www.example.com allows
+# access to ~www.example.com/ features/news.html, etc.
+#
+# Or, you can designate sites as trusted referrers, by prepending
+# the name with a + character. The effect is that access to
+# untrusted sites will be granted -- but only if a link from
+# this trusted referrer was used to get there. The link target
+# will then be added to the "trustfile" so that future, direct
+# accesses will be granted. Sites added via this mechanism do
+# not become trusted referrers themselves (i.e. they are added
+# with a ~ designation). There is a limit of 512 such entries,
+# after which new entries will not be made.
+#
+# If you use the + operator in the trust file, it may grow
+# considerably over time.
+#
+# It is recommended that Privoxy be compiled with the
+# --disable-force, --disable-toggle and --disable-editor options,
+# if this feature is to be used.
+#
+# Possible applications include limiting Internet access for
+# children.
+#
+#trustfile trust
+#
+#
+# 3. DEBUGGING
+# =============
+#
+# These options are mainly useful when tracing a problem. Note that
+# you might also want to invoke Privoxy with the --no-daemon command
+# line option when debugging.
+#
+#
+#
+# 3.1. debug
+# ===========
+#
+# Specifies:
+#
+# Key values that determine what information gets logged.
+#
+# Type of value:
+#
+# Integer values
+#
+# Default value:
+#
+# 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
+#
+# Effect if unset:
+#
+# Default value is used (see above).
+#
+# Notes:
+#
+# The available debug levels are:
+#
+# 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 16 # log all data written to the network into the logfile
+# debug 32 # debug force feature
+# debug 64 # debug regular expression filters
+# debug 128 # debug redirects
+# debug 256 # debug GIF de-animation
+# debug 512 # Common Log Format
+# 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
+#
+#
+# To select multiple debug levels, you can either add them or
+# use multiple debug lines.
+#
+# A debug level of 1 is informative because it will show you each
+# request as it happens. 1, 4096 and 8192 are recommended so that
+# you will notice when things go wrong. The other levels are
+# probably only of interest if you are hunting down a specific
+# problem. They can produce a hell of an output (especially 16).
+#
+# Privoxy used to ship with the debug levels recommended above
+# enabled by default, but due to privacy concerns 3.0.7 and later
+# are configured to only log fatal errors.
+#
+# If you are used to the more verbose settings, simply enable
+# the debug lines below again.
+#
+# If you want to use pure CLF (Common Log Format), you should set
+# "debug 512" ONLY and not enable anything else.
+#
+# Privoxy has a hard-coded limit for the length of log messages. If
+# it's reached, messages are logged truncated and marked with
+# "... [too long, truncated]".
+#
+# Please don't file any support requests without trying to
+# reproduce the problem with increased debug level first. Once
+# you read the log messages, you may even be able to solve the
+# problem on your own.
+#
+#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
+#
+#
+# 3.2. single-threaded
+# =====================
+#
+# Specifies:
+#
+# Whether to run only one server thread.
+#
+# Type of value:
+#
+# None
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#