-# Sample Configuration file for the Internet Junkbuster 2.0
-
-#
-# $Id: config,v 1.2 2001/04/30 03:05:11 rodney Exp $
-#
-
-#
-#
-# Copyright 1997-8 Junkbusters Corp. For distribution, modification and use
-# under the GNU General Public License. These files come with NO WARRANTY.
-# See http://www.junkbusters.com/ht/en/gpl.html or README file for details.
-#
-# When starting the proxy, give the name of this file as an argument.
-# Any changes made to this file are *not* automatically loaded; you have
-# to stop and restart the proxy.
-
-# For information see http://www.junkbusters.com/ht/en/ijbman.html
-# or the documentation that came with the release
-
-# Lines beginning with a # character are comments; they are ignored.
-# Many example lines are provided here commented out
-
-# the blockfile contains patterns to be blocked by the proxy
-blockfile ./blocklist # comments are OK here, too
-
-# the imagefile contains patterns to detect blocked images
-imagefile ./imagelist
-
-# the popfile contains patterns of servers where javascript popups are disabled
-#
-# if the next line is not commented out, all javascript popups from the sites
-# that match the patterns in popup will be blocked
-# popupfile ./popup
-
-# File containing content modification rules
-#re_filterfile ./re_filterfile
-
-# Uncomment to filter *all* traffic. Default is to
-# filter only if we wouldn't send a cookie either.
-#
-#re_filter_all
-
-
-# the cookiefile contains patterns to specify the cookie management policy
-#
-cookiefile ./cookiefile
-
-# the logfile is where all logging and error messages are written
-#
-logfile ./junkbuster.log
-
-# the jarfile is where cookies can be stored
-#
-#jarfile ./jarfile
-
-# the forwardfile defines domain-specific routing
-#
-#forwardfile ./forward
-
-# file which lists and into which trusted domains are written
-#
-#trustfile ./trust
-# files specify locations of "for information about trusted referers, see.."
-# multiple trust_info_url lines are OK
-#
-# trust_info_url http://internet.junkbuster.com/
-# trust_info_url http://www.yoursite.com/our_trust_policy.html
-#
-
-# The access control list file can be used to restrict IP addresses
-# that are permitted to use the proxy (see warnings in the FAQ).
-#
-#aclfile ./aclfile
-
-# add an "X-Forwarded-For:" specification to each request header
-#
-#add-forwarded-header
-
-# if logging cookies into a jarfile, and no other wafers were
-# explicity set, then by default a vanilla wafer is sent with
-# each request.
-#
-# setting 'suppress-vanilla-wafer' stops this vanilla wafer from
-# being sent.
-#
-suppress-vanilla-wafer
-
-# add these wafers to each request header
-# multiple wafer lines are OK
-#
-#wafer NOTE=Like most people, I want my browsing to be anonymous.
-#wafer WARNING=Please do not attempt to track me.
-
-# Anything can be added to the request headers. Please don't litter.
-# multiple add-header lines are OK
-#
-#add-header Forwarded: by http://stay-out-of-my-backyard.net
-#add-header Forwarded: by http://pro-privacy-isp.net
-#add-header Proxy-Connection: Keep-Alive
-
-# listen-address specifies where the Junkbuster will listen for connections
-# Specifying a port is optional; if unspecified the defaults is 8000.
-# Before Version 2.0.2 the default was to bind to all IP addresses (INADDR_ANY)
-# This has been restricted to localhost to avoid unintended security breaches.
-# To open the proxy to all, uncomment the following line:
-#listen-address :8000
-# other example usage:
-#listen-address 124.207.250.245:8080
-# to explicitly state what is now the default:
-#listen-address localhost
-# or equivalently:
-listen-address 127.0.0.1:8000
-
-# user-agent specifies treatment of the "User-Agent:" (and "UA-*:") header(s)
-# default: Forge the "User-Agent:"
-# 'text' : Always send <text> as the "User-Agent:"
-# . : Pass the "User-Agent:" unchanged
-# @ : Pass the "User-Agent:" if the server is in the cookie file,
-# forge the "User-Agent:" otherwise
-#user-agent @
-
-# note: Russian browsers may be confused if user agent misidentifies
-# the operating system (Mac vs Windows); see FAQ
-user-agent .
-
-# referer specifies treatment of the "Referer:" header
-# New option by "Andreas S. Oesterhelt" <oes@paradis.rhein.de>
-#
-# default: Kill the referrer-header from the client
-# 'text' : Always send <text> as the referrer
-# . : Pass the referrer unchanged
-# @ : Pass the referrer if the server is in the cookie file,
-# kill the referrer otherwise
-# § : Pass the referrer if the server is in the cookie file,
-# send a forged referrer that points to the root-diretory URL
-# of the current request otherwise
-referer §
-
-# from specifies value to be subsituted if browser provides a "From:" header
-#
-#from spam-me-senseless@sittingduck.net
-
-# tinygif allows you to change the appearance of blocked images
-#
-# tinygif 0 # Show a "broken icon"
-# tinygif 1 # Show a GIF of one transparent pixel
-# tinygif 2 # Show a GIF with the word "JUNKBUSTER"
-tinygif 2
-# tinygif 3 http://localhost/1x1.gif # Temporary redirect to this URL
-
-# Andrew <anw@tirana.freewire.co.uk> added
-# The following can be used to suppress display of the block lists when the
-# page http://x.x/show-proxy-args is displayed. With a long block list this
-# accelerates loading of the configuration page and also hides the contents of
-# the block lists (for whatever reason). Maintainers of junkbuster proxies for
-# multiple use can specify a message for any use who wants to know what is in
-# these files.
-#
-#suppress-blocklists Contact sysadmin@example.com for details.
-# suppress-blocklists
-
-# debug sets the level of debugging information to log in the logfile
-#
-# debug 1 # GPC = show each GET/POST/CONNECT request
-# debug 2 # CONN = show each connection status
-# debug 4 # IO = show I/O status
-# debug 8 # HDR = show header parsing
-# debug 16 # LOG = log all data into the logfile
-# debug 32 # FRC = debug force feature
-# debug 64 # REF = debug regular expression filter
-#
-# multiple "debug" directives, are OK - they're logical-OR'd together
-#
-#debug 15 # same as setting the first 4 listed above
-debug 1
-#debug 255
-
-# single-threaded operation (i.e. disallows multiple threads or processes)
-# This is most often used for debugging because it keeps the
-# debugging output "in order" for easy reading.
-#
+# Sample Configuration File for Privoxy v3.1.1
+#
+# Copyright (C) 2001, 2002 Privoxy Developers http://privoxy.org
+#
+# $Id: config,v 1.39.2.6 2002/08/25 23:50:21 hal9 Exp $
+#
+####################################################################
+# #
+# Table of Contents #
+# #
+# I. INTRODUCTION #
+# II. FORMAT OF THE CONFIGURATION FILE #
+# #
+# 1. CONFIGURATION AND LOG FILE LOCATIONS #
+# 2. LOCAL SET-UP DOCUMENTATION #
+# 3. DEBUGGING #
+# 4. ACCESS CONTROL AND SECURITY #
+# 5. FORWARDING #
+# 6. WINDOWS GUI OPTIONS #
+# #
+####################################################################
+#
+#
+# I. INTRODUCTION
+# ===============
+#
+# This file holds the Privoxy configuration. If you modify this file,
+# you will need to send a couple of requests to the proxy before any
+# changes take effect.
+#
+# When starting Privoxy on Unix systems, give the name of this file as
+# an argument. On Windows systems, Privoxy will look for this file
+# with the name 'config.txt' in the same directory where Privoxy
+# is installed.
+#
+#
+# II. FORMAT OF THE CONFIGURATION FILE
+# ====================================
+#
+# Configuration lines consist of an initial keyword followed by a
+# list of values, all separated by whitespace (any number of spaces
+# or tabs). For example,
+#
+# actionsfile default.action
+#
+# Indicates that the actionsfile is named 'default.action'.
+#
+# The '#' indicates a comment. Any part of a line following a '#'
+# is ignored, except if the '#' is preceded by a '\'.
+#
+# Thus, by placing a # at the start of an existing configuration line,
+# you can make it a comment and it will be treated as if it weren't
+# there. This is called "commenting out" an option and can be useful.
+#
+# Note that commenting out and option and leaving it at its default
+# are two completely different things! Most options behave very
+# differently when unset. See the the "Effect if unset" explanation
+# in each option's description for details.
+#
+# Long lines can be continued on the next line by using a `\' as the
+# last character.
+#
+
+#
+# 1. CONFIGURATION AND LOG FILE LOCATIONS
+# =======================================
+#
+# Privoxy can (and normally does) use a number of other files for
+# additional configuration, help and logging. This section of the
+# configuration file tells Privoxy where to find those other files.
+#
+# The user running Privoxy, must have read permission for all
+# configuration files, and write permission to any files that would
+# be modified, such as log files and actions files.
+#
+
+#
+# 1.1. confdir
+# ============
+#
+# Specifies:
+#
+# The directory where the other configuration files are located
+#
+# Type of value:
+#
+# Path name
+#
+# Default value:
+#
+# /etc/privoxy (Unix) or Privoxy installation dir (Windows)
+#
+# Effect if unset:
+#
+# Mandatory
+#
+# Notes:
+#
+# No trailing "/", please
+#
+# When development goes modular and multi-user, the blocker,
+# filter, and per-user config will be stored in subdirectories of
+# "confdir". For now, the configuration directory structure is
+# flat, except for confdir/templates, where the HTML templates
+# for CGI output reside (e.g. Privoxy's 404 error page).
+#
+confdir .
+
+#
+# 1.2. logdir
+# ===========
+#
+# Specifies:
+#
+# The directory where all logging takes place (i.e. where logfile
+# and jarfile are 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 .
+
+#
+# 1.3. actionsfile
+# ================
+#
+# Specifies:
+#
+# The actions file(s) to use
+#
+# Type of value:
+#
+# File name, relative to confdir, without the .action suffix
+#
+# Default values:
+#
+# standard # Internal purposes, no editing recommended
+#
+# default # Main actions file
+#
+# user # User customizations
+#
+# Effect if unset:
+#
+# No actions are taken at all. Simple 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 are where all the per site and per URL
+# configuration is done for ad blocking, cookie management,
+# privacy considerations, etc. There is no point in using Privoxy
+# without at least one actions file.
+#
+actionsfile standard # Internal purpose, recommended
+actionsfile default # Main actions file
+actionsfile user # User customizations
+
+#
+# 1.4. filterfile
+# ===============
+#
+# Specifies:
+#
+# The filter file 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:
+#
+# The filter file contains content modification rules that use
+# regular expressions. These rules permit powerful changes on the
+# content of Web pages, e.g., you could disable your favorite
+# JavaScript annoyances, re-write the actual displayed text,
+# or just have some fun replacing "Microsoft" with "MicroSuck"
+# wherever it appears on a Web page.
+#
+# The +filter{name} actions rely on the relevant filter (name)
+# to be defined in the filter file!
+#
+# A pre-defined filter file called default.filter that contains
+# a bunch of handy filters for common problems is included in the
+# distribution. See the section on the filter action for a list.
+#
+filterfile default.filter
+
+#
+# 1.5. logfile
+# ============
+#
+# Specifies:
+#
+# The log file to use
+#
+# Type of value:
+#
+# File name, relative to logdir
+#
+# Default value:
+#
+# logfile (Unix) or privoxy.log (Windows)
+#
+# Effect if unset:
+#
+# No log file is used, all log messages go to the console (STDERR).
+#
+# Notes:
+#
+# The windows version will additionally log to the console.
+#
+# 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) but in most cases you probably
+# will never look at it.
+#
+# 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, a logrotate
+# script has been included.
+#
+# On SuSE Linux systems, you can place a line like
+# "/var/log/privoxy.* +1024k 644 nobody.nogroup" in /etc/logfiles,
+# with the effect that cron.daily will automatically archive,
+# gzip, and empty the log, when it exceeds 1M size.
+#
+# Any log files must be writable by whatever user Privoxy is
+# being run as (default on UNIX, user id is "privoxy").
+#
+logfile logfile
+
+#
+# 1.6. jarfile
+# ============
+#
+# Specifies:
+#
+# The file to store intercepted cookies in
+#
+# Type of value:
+#
+# File name, relative to logdir
+#
+# Default value:
+#
+# jarfile (Unix) or privoxy.jar (Windows)
+#
+# Effect if unset:
+#
+# Intercepted cookies are not stored at all.
+#
+# Notes:
+#
+# The jarfile may grow to ridiculous sizes over time.
+#
+jarfile jarfile
+
+#
+# 1.7. trustfile
+# ==============
+#
+# Specifies:
+#
+# 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 whole trust mechanism is turned off.
+#
+# 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 named in the trustfile. You can also mark sites
+# as trusted referrers (with +), with the effect that access
+# to untrusted sites will be granted, if a link from a trusted
+# referrer was used. The link target will then be added to the
+# "trustfile". Possible applications include limiting Internet
+# access for children.
+#
+# If you use + operator in the trust file, it may grow considerably
+# over time.
+#
+#trustfile trust
+
+#
+# 2. LOCAL SET-UP DOCUMENTATION
+# =============================
+#
+# If you intend to operate Privoxy for more users than just yourself,
+# it might be a good idea to let them know how to reach you, what
+# you block and why you do that, your policies, etc.
+#
+
+#
+# 2.1. user-manual
+# ================
+#
+# Specifies:
+#
+# Location of the Privoxy User Manual.
+#
+# Type of value:
+#
+# A fully qualified URI
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# http://www.privoxy.org/version/user-manual/ will be used,
+# where version is the Privoxy version.
+#
+# Notes:
+#
+# The User Manual URI is used for help links from some of the
+# internal CGI pages. The manual itself is normally packaged
+# with the binary distributions, so you probably want to set this
+# to a locally installed copy. For multi-user setups, you could
+# provide a copy on a local webserver for all your users and use
+# the corresponding URL here.
+#
+# Examples:
+#
+# Unix, in local filesystem:
+#
+# user-manual file:///usr/share/doc/privoxy-2.9.18/user-manual/
+#
+# Any platform, on local webserver (called "local-webserver"):
+#
+# user-manual http://local-webserver/privoxy-user-manual/
+#
+# WARNING!!!
+#
+# 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/
+
+#
+# 2.2. trust-info-url
+# ===================
+#
+# Specifies:
+#
+# A URL to be displayed in the error page that users will see if
+# access to an untrusted page is denied.
+#
+# Type of value:
+#
+# URL
+#
+# Default value:
+#
+# Two example URL are provided
+#
+# Effect if unset:
+#
+# No links are displayed on the "untrusted" error page.
+#
+# Notes:
+#
+# The value of this option only matters if the experimental trust
+# mechanism has been activated. (See trustfile above.)
+#
+# If you use the trust mechanism, it is a good idea to write
+# up some on-line documentation about your trust policy and to
+# specify the URL(s) here. Use multiple times for multiple URLs.
+#
+# The URL(s) should be added to the trustfile as well, so users
+# 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
+
+#
+# 2.3. admin-address
+# ==================
+#
+# Specifies:
+#
+# An email address to reach the proxy administrator.
+#
+# Type of value:
+#
+# Email address
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# No email address is displayed on error pages and the CGI user
+# interface.
+#
+# Notes:
+#
+# If both admin-address and proxy-info-url are unset, the whole
+# "Local Privoxy Support" box on all generated pages will not
+# be shown.
+#
+#admin-address privoxy-admin@example.com
+
+#
+# 2.4. proxy-info-url
+# ===================
+#
+# Specifies:
+#
+# A URL to documentation about the local Privoxy setup,
+# configuration or policies.
+#
+# Type of value:
+#
+# URL
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# No link to local documentation is displayed on error pages and
+# the CGI user interface.
+#
+# Notes:
+#
+# If both admin-address and proxy-info-url are unset, the whole
+# "Local Privoxy Support" box on all generated pages will not
+# be shown.
+#
+# This URL shouldn't be blocked ;-)
+#
+#proxy-info-url http://www.example.com/proxy-service.html
+
+#
+# 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 to
+# the logfile.
+#
+# Type of value:
+#
+# Integer values
+#
+# Default value:
+#
+# 12289 (i.e.: URLs plus informational and warning messages)
+#
+# Effect if unset:
+#
+# Nothing gets logged.
+#
+# Notes:
+#
+# The available debug levels are:
+#
+# debug 1 # show each GET/POST/CONNECT request
+# debug 2 # show each connection status
+# debug 4 # show I/O status
+# debug 8 # show header parsing
+# debug 16 # log all data into the logfile
+# debug 32 # debug force feature
+# debug 64 # debug regular expression filter
+# debug 128 # debug fast redirects
+# debug 256 # debug GIF de-animation
+# debug 512 # Common Log Format
+# debug 1024 # debug kill pop-ups
+# 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 highly 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).
+#
+# The reporting of fatal errors (i.e. ones which crash Privoxy)
+# is always on and cannot be disabled.
+#
+# If you want to use CLF (Common Log Format), you should set
+# "debug 512" ONLY and not enable anything else.
+#
+debug 1 # show each GET/POST/CONNECT request
+debug 4096 # Startup banner and warnings
+debug 8192 # Errors - *we highly recommended enabling this*
+
+#
+# 3.2. single-threaded
+# ====================
+#
+# Specifies:
+#
+# Whether to run only one server thread
+#
+# Type of value:
+#
+# None
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# Multi-threaded (or, where unavailable: forked) operation,
+# i.e. the ability to serve multiple requests simultaneously.
+#
+# Notes:
+#
+# This option is only there for debug purposes and you should
+# never need to use it. It will drastically reduce performance.
+#