-#
-# 'toggle' allows you to temporarily disable all Junkbuster's
-# filtering. Just set "toggle 0".
-#
-# The Windows version of Junkbuster puts an icon in the system
-# tray, which allows you to change this option without having
-# to edit this file. If you right-click on that icon (or select
-# the 'Options' menu), one choice is "Enable". Clicking on enable
-# toggles Junkbuster on and off. This is useful if you want to
-# temporarily disable Junkbuster, e.g., to access a site that
-# requires cookies which you normally have blocked.
-#
-# 'toggle 1' means Junkbuster runs normally, 'toggle 0' means
-# that Junkbuster becomes a non-anonymizing non-blocking
-# proxy.
-#
-# Default: 1
-#
-toggle 1
-
-
-#############################################################################
-# Access Control List
-#############################################################################
-#
-# Access controls are included at the request of some ISPs and systems
-# administrators, and are not usually needed by individual users.
-# Please note the warnings in the FAQ that this proxy is not
-# intended to be a substitute for a firewall or to encourage anyone
-# to defer addressing basic security weaknesses.
-# For details see the documentation
-#
-# If no access settings are specified, the proxy talks to anyone that
-# connects. If any access settings file are specified, then the proxy
-# talks only to IP addresses permitted somewhere in this file and not
-# denied later in this file.
-#
-# Summary -- if using an ACL:
-#
-# Client must have permission to receive service
-# LAST match in ACL wins
-# Default behavior is to deny service
-#
-# Syntax for an entry in the Access Control List is:
-#
-# ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
-#
-# where the fields are
-#
-# ACTION = "permit-access" | "deny-access"
-#
-# SRC_ADDR = client hostname or dotted IP address
-# SRC_MASKLEN = number of bits in the subnet mask for the source
-#
-# DST_ADDR = server or forwarder hostname or dotted IP address
-# DST_MASKLEN = number of bits in the subnet mask for the target
-#
-# field separator (FS) is whitespace (space or tab)
-#
-# IMPORTANT NOTE
-# ==============
-# If the junkbuster is using a forwarder or a gateway for a particular
-# destination URL, the DST_ADDRR that is examined is the address of
-# the forwarder or the gateway and NOT the address of the ultimate target.
-# This is necessary because it may be impossible for the local
-# junkbuster to determine the address of the ultimate target
-# (that's often what gateways are used for).
-#
-# Here are a few examples to show how the ACL works:
-#
-# localhost is OK -- no DST_ADDR implies that ALL destination addresses are OK
-# permit-access localhost
-#
-# a silly example to illustrate:
-#
-# permit any host on the class-C subnet with junkbusters to go anywhere
-#
-# permit-access www.junkbusters.com/24
-#
-# except deny one particular IP address from using it at all
-#
-# deny-access ident.junkbusters.com
-#
-# another example
-#
-# You can specify an explicit network address and subnet mask.
-# Explicit addresses do not have to be resolved to be used.
-#
-# permit-access 207.153.200.0/24
-#
-# a subnet mask of 0 matches anything, so the next line permits everyone.
-#
-# permit-access 0.0.0.0/0
-#
-# Note: you cannot say
-#
-# permit-access .org
-#
-# to allow all .org domains; every IP-address listed must resolve fully.
-#
-# An ISP may want to provide a junkbuster that is accessible by "the world"
-# and yet restrict use of some of their private content to hosts on its
-# internal network (i.e. its own subscribers). Say, for instance the
-# ISP owns the Class-B IP address block 123.124.0.0 (a 16 bit netmask).
-# This is how they could do it:
-#
-# permit-access 0.0.0.0/0 0.0.0.0/0 # other clients can go anywhere
-# # with the following exceptions:
-#
-# deny-access 0.0.0.0/0 123.124.0.0/16 # block all external requests for
-# # sites on the ISP's network
-#
-# permit 0.0.0.0/0 www.my_isp.com # except for the ISP's main web site
-#
-# permit 123.124.0.0/16 0.0.0.0/0 # the ISP's clients can go anywhere
-#
-# Note that some hostnames may be listed with multiple IP addresses;
-# the primary value returned by gethostbyname() is used.
-#
-# Default: Anyone can access the proxy.
-
-
-#############################################################################
-# Forwarding
-#############################################################################
-#
-#
-# This feature allows routing of HTTP requests via multiple proxies.
-# It can be used to better protect privacy and confidentiality when
-# accessing specific domains by routing requests to those domains
-# to a special purpose filtering proxy such as lpwa.com
-#
-# It can also be used in an environment with multiple networks to route
-# requests via multiple gateways allowing transparent access to multiple
-# networks without having to modify browser configurations.
-#
-# Also specified here are SOCKS proxies. We support SOCKS 4 and SOCKS 4A.
-# The difference is that SOCKS 4A will resolve the target hostname using
-# DNS on the SOCKS server, not our local DNS client.
-#
-# The syntax of each line is
-#
-# forward target_domain[:port] http_proxy_host[:port]
-# forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]
-# forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]
-#
-# If http_proxy_host is ".", then requests are not forwarded to
-# a HTTP proxy but are made directly to the web servers.
-#
-# Lines are checked in turn, and the last match wins.
-#
-# There is an implicit line equivalent to the following, which specifies that
-# anything not finding a match on the list is to go out without forwarding
-# or gateway protocol; like so:
-# forward .* . # implicit
-#
-# In the following common configuration, everything goes to Lucent's LPWA,
-# except SSL on port 443 (which it doesn't handle)
-# forward .* lpwa.com:8000
-# forward :443 .
-#
-# See the FAQ for instructions on how to automate the login procedure for LPWA.
-# Some users have reported difficulties related to LPWA's use of . as the
-# last element of the domain, and have said that this can be fixed with this:
-# forward lpwa. lpwa.com:8000
-# (NOTE: the syntax for specifiying target_domain has changed since the
-# previous paragraph weas written - it will not work now. More information
-# is welcome.)
-#
-# In this fictitious example, everything goes via an ISP's caching proxy,
-# except requests to that ISP:
-#
-# forward .* caching.myisp.net:8000
-# forward myisp.net .
-#
-# For the @home network, we're told the forwarding configuration is this:
-# forward .* proxy:8080
-# Also, we're told they insist on getting cookies and Javascript, so you need
-# to add home.com to the cookie file. We consider Javascript a security risk;
-# see our page on cookies. Java need not be enabled.
-#
-# In this example direct connections are made to all "internal" domains,
-# but everything else goes through Lucent's LPWA by way of the company's
-# SOCKS gateway to the Internet.
-#
-# forward_socks4 .* lpwa.com:8000 firewall.my_company.com:1080
-# forward my_company.com .
-#
-# This is how you could set up a site that always uses SOCKS but no forwarders
-#
-# forward_socks4a .* . firewall.my_company.com:1080
-#
-# An advanced example for network administrators:
-#
-# If you have links to multiple ISPs that provide various special content to
-# their subscribers, you can configure forwarding to pass requests to the
-# specific host that's connected to that ISP so that everybody can see all
-# of the content on all of the ISPs.
-#
-# This is tricky, but here's a sample:
-#
-# host-a has a PPP connection to isp-a.com
-# host-b has a PPP connection to isp-b.com
-#
-# host-a can run an Internet Junkbuster proxy with forwarding like this:
-# forward .* .
-# forward isp-b.com host-b:8000
-#
-# host-b can run an Internet Junkbuster proxy with forwarding like this:
-# forward .* .
-# forward isp-a.com host-a:8000
-#
-# Now, *anyone* on the Internet (including users on host-a and host-b)
-# can set their browser's proxy to *either* host-a or host-b and
-# be able to browse the content on isp-a or isp-b.
-#
-#
-# Here's another practical example, for University of Kent at
-# Canterbury students with a network connection in their room, who
-# need to use the University's Squid web cache.
-#
-# forward *. ssbcache.ukc.ac.uk:3128 # Use the proxy, except for:
-# forward .ukc.ac.uk . # Anything on the same domain as us
-# forward * . # Host with no domain specified
-# forward 129.12.*.* . # A dotted IP on our /16 network.
-# forward 127.*.*.* . # Loopback address
-# forward localhost.localdomain . # Loopback address
-# forward www.ukc.mirror.ac.uk . # Specific host
-#
-
-
-#############################################################################
-# 5. WINDOWS GUI OPTIONS
-#############################################################################
-#
-# Junkbuster has a number of options specific to the Windows GUI
+#
+# 4. ACCESS CONTROL AND SECURITY
+# ==============================
+#
+# This section of the config file controls the security-relevant
+# aspects of Privoxy's configuration.
+#
+
+#
+# 4.1. listen-address
+# ===================
+#
+# Specifies:
+#
+# The IP address and TCP port on which Privoxy will listen for
+# client requests.
+#
+# Type of value:
+#
+# [IP-Address]:Port
+#
+# Default value:
+#
+# 127.0.0.1:8118
+#
+# Effect if unset:
+#
+# Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
+# recommended for home users who run Privoxy on the same machine
+# as their browser.
+#
+# Notes:
+#
+# You will need to configure your browser(s) to this proxy address
+# and port.
+#
+# If you already have another service running on port 8118, or
+# if you want to serve requests from other machines (e.g. on your
+# local network) as well, you will need to override the default.
+#
+# If you leave out the IP address, Privoxy will bind to all
+# interfaces (addresses) on your machine and may become reachable
+# from the Internet. In that case, consider using access control
+# lists (ACL's, see below), and/or a firewall.
+#
+# If you open Privoxy to untrusted users, you will also want
+# to turn off the enable-edit-actions and enable-remote-toggle
+# options!
+#
+# Example:
+#
+# Suppose you are running Privoxy on a machine which has the
+# address 192.168.0.1 on your local private network (192.168.0.0)
+# and has another outside connection with a different address. You
+# want it to serve requests from inside only:
+#
+# listen-address 192.168.0.1:8118
+#
+listen-address 127.0.0.1:8118
+
+#
+# 4.2. toggle
+# ===========
+#
+# Specifies:
+#
+# Initial state of "toggle" status
+#
+# Type of value:
+#
+# 1 or 0
+#
+# Default value:
+#
+# 1
+#
+# Effect if unset:
+#
+# Act as if toggled on
+#
+# Notes:
+#
+# If set to 0, Privoxy will start in "toggled off" mode,
+# i.e. behave like a normal, content-neutral proxy where all ad
+# blocking, filtering, etc are disabled. See enable-remote-toggle
+# below. This is not really useful anymore, since toggling is
+# much easier via the web interface than via editing the conf file.
+#
+# The windows version will only display the toggle icon in the
+# system tray if this option is present.
+#
+toggle 1
+
+#
+# 4.3. enable-remote-toggle
+# =========================
+#
+# Specifies:
+#
+# Whether or not the web-based toggle feature may be used
+#
+# Type of value:
+#
+# 0 or 1
+#
+# Default value:
+#
+# 1
+#
+# Effect if unset:
+#
+# The web-based toggle feature is disabled.
+#
+# Notes:
+#
+# When toggled off, Privoxy acts like a normal, content-neutral
+# proxy, i.e. it acts as if none of the actions applied to
+# any URL.
+#
+# For the time being, access to the toggle feature can not be
+# controlled separately by "ACLs" or HTTP authentication, so that
+# everybody who can access Privoxy (see "ACLs" and listen-address
+# above) can toggle it for all users. So this option is not
+# recommended for multi-user environments with untrusted users.
+#
+# Note that you must have compiled Privoxy with support for this
+# feature, otherwise this option has no effect.
+#
+enable-remote-toggle 1
+
+#
+# 4.4. enable-edit-actions
+# ========================
+#
+# Specifies:
+#
+# Whether or not the web-based actions file editor may be used
+#
+# Type of value:
+#
+# 0 or 1
+#
+# Default value:
+#
+# 1
+#
+# Effect if unset:
+#
+# The web-based actions file editor is disabled.
+#
+# Notes:
+#
+# For the time being, access to the editor can not be controlled
+# separately by "ACLs" or HTTP authentication, so that everybody
+# who can access Privoxy (see "ACLs" and listen-address above)
+# can modify its configuration for all users. So this option is
+# not recommended for multi-user environments with untrusted users.
+#
+# Note that you must have compiled Privoxy with support for this
+# feature, otherwise this option has no effect.
+#
+enable-edit-actions 1
+
+#
+# 4.5. ACLs: permit-access and deny-access
+# ========================================
+#
+# Specifies:
+#
+# Who can access what.
+#
+# Type of value:
+#
+# src_addr[/src_masklen] [dst_addr[/dst_masklen]]
+#
+# Where src_addr and dst_addr are IP addresses in dotted decimal
+# notation or valid DNS names, and src_masklen and dst_masklen are
+# subnet masks in CIDR notation, i.e. integer values from 2 to 30
+# representing the length (in bits) of the network address. The
+# masks and the whole destination part are optional.
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# Don't restrict access further than implied by listen-address
+#
+# Notes:
+#
+# Access controls are included at the request of ISPs and systems
+# administrators, and are not usually needed by individual
+# users. For a typical home user, it will normally suffice to
+# ensure that Privoxy only listens on the localhost (127.0.0.1)
+# or internal (home) network address by means of the listen-address
+# option.
+#
+# Please see the warnings in the FAQ that this proxy is not
+# intended to be a substitute for a firewall or to encourage
+# anyone to defer addressing basic security weaknesses.
+#
+# Multiple ACL lines are OK. If any ACLs are specified, then
+# the Privoxy talks only to IP addresses that match at least one
+# permit-access line and don't match any subsequent deny-access
+# line. In other words, the last match wins, with the default
+# being deny-access.
+#
+# If Privoxy is using a forwarder (see forward below) for a
+# particular destination URL, the dst_addr that is examined is
+# the address of the forwarder and NOT the address of the ultimate
+# target. This is necessary because it may be impossible for the
+# local Privoxy to determine the IP address of the ultimate target
+# (that's often what gateways are used for).
+#
+# You should prefer using IP addresses over DNS names, because
+# the address lookups take time. All DNS names must resolve! You
+# can not use domain patterns like "*.org" or partial domain
+# names. If a DNS name resolves to multiple IP addresses, only
+# the first one is used.
+#
+# Denying access to particular sites by ACL may have undesired
+# side effects if the site in question is hosted on a machine
+# which also hosts other sites.
+#
+# Examples:
+#
+# Explicitly define the default behavior if no ACL and
+# listen-address are set: "localhost" is OK. The absence of a
+# dst_addr implies that all destination addresses are OK:
+#
+# permit-access localhost
+#
+# Allow any host on the same class C subnet as www.privoxy.org
+# access to nothing but www.example.com:
+#
+# permit-access www.privoxy.org/24 www.example.com/32
+#
+# Allow access from any host on the 26-bit subnet 192.168.45.64
+# to anywhere, with the exception that 192.168.45.73 may not
+# access www.dirty-stuff.example.com:
+#
+# permit-access 192.168.45.64/26
+# deny-access 192.168.45.73 www.dirty-stuff.example.com
+#
+
+#
+# 4.6. buffer-limit
+# =================
+#
+# Specifies:
+#
+# Maximum size of the buffer for content filtering.
+#
+# Type of value:
+#
+# Size in Kbytes
+#
+# Default value:
+#
+# 4096
+#
+# Effect if unset:
+#
+# Use a 4MB (4096 KB) limit.
+#
+# Notes:
+#
+# For content filtering, i.e. the +filter and +deanimate-gif
+# actions, it is necessary that Privoxy buffers the entire document
+# body. This can be potentially dangerous, since a server could
+# just keep sending data indefinitely and wait for your RAM to
+# exhaust -- with nasty consequences. Hence this option.
+#
+# When a document buffer size reaches the buffer-limit, it is
+# flushed to the client unfiltered and no further attempt to filter
+# the rest of the document is made. Remember that there may be
+# multiple threads running, which might require up to buffer-limit
+# Kbytes each, unless you have enabled "single-threaded" above.
+#
+buffer-limit 4096
+
+#
+# 5. FORWARDING
+# =============
+#
+# This feature allows routing of HTTP requests through a chain
+# of multiple proxies. It can be used to better protect privacy
+# and confidentiality when accessing specific domains by routing
+# requests to those domains through an anonymous public proxy (see
+# e.g. http://www.multiproxy.org/anon_list.htm) Or to use a caching
+# proxy to speed up browsing. Or chaining to a parent proxy may be
+# necessary because the machine that Privoxy runs on has no direct
+# Internet access.
+#
+# Also specified here are SOCKS proxies. Privoxy supports the SOCKS
+# 4 and SOCKS 4A protocols.
+#
+
+#
+# 5.1. forward
+# ============
+#
+# Specifies:
+#
+# To which parent HTTP proxy specific requests should be routed.
+#
+# Type of value:
+#
+# target_pattern http_parent[:port]
+#
+# where target_pattern is a URL pattern that specifies to which
+# requests (i.e. URLs) this forward rule shall apply. Use /
+# to denote "all URLs". http_parent[:port] is the DNS name or
+# IP address of the parent HTTP proxy through which the requests
+# should be forwarded, optionally followed by its listening port
+# (default: 8080). Use a single dot (.) to denote "no forwarding".
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# Don't use parent HTTP proxies.
+#
+# Notes:
+#
+# If http_parent is ".", then requests are not forwarded to
+# another HTTP proxy but are made directly to the web servers.
+#
+# Multiple lines are OK, they are checked in sequence, and the
+# last match wins.
+#
+# Examples:
+#
+# Everything goes to an example anonymizing proxy, except SSL on
+# port 443 (which it doesn't handle):
+#
+# forward / anon-proxy.example.org:8080
+# forward :443 .
+#
+# Everything goes to our example ISP's caching proxy, except for
+# requests to that ISP's sites:
+#
+# forward / caching-proxy.example-isp.net:8000
+# forward .example-isp.net .
+#
+
+#
+# 5.2. forward-socks4 and forward-socks4a
+# =======================================
+#
+# Specifies:
+#
+# Through which SOCKS proxy (and to which parent HTTP proxy)
+# specific requests should be routed.
+#
+# Type of value:
+#
+# target_pattern socks_proxy[:port] http_parent[:port]
+#
+# where target_pattern is a URL pattern that specifies to which
+# requests (i.e. URLs) this forward rule shall apply. Use / to
+# denote "all URLs". http_parent and socks_proxy are IP addresses
+# in dotted decimal notation or valid DNS names (http_parent may
+# be "." to denote "no HTTP forwarding"), and the optional port
+# parameters are TCP ports, i.e. integer values from 1 to 64535
+#
+# Default value:
+#
+# Unset
+#
+# Effect if unset:
+#
+# Don't use SOCKS proxies.
+#
+# Notes:
+#
+# Multiple lines are OK, they are checked in sequence, and the
+# last match wins.
+#
+# The difference between forward-socks4 and forward-socks4a
+# is that in the SOCKS 4A protocol, the DNS resolution of the
+# target hostname happens on the SOCKS server, while in SOCKS 4
+# it happens locally.
+#
+# If http_parent is ".", then requests are not forwarded to another
+# HTTP proxy but are made (HTTP-wise) directly to the web servers,
+# albeit through a SOCKS proxy.
+#
+# Examples:
+#
+# From the company example.com, direct connections are made to all
+# "internal" domains, but everything outbound goes through their
+# ISP's proxy by way of example.com's corporate SOCKS 4A gateway
+# to the Internet.
+#
+# forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
+# forward .example.com .
+#
+# A rule that uses a SOCKS 4 gateway for all destinations but no
+# HTTP parent looks like this:
+#
+# forward-socks4 / socks-gw.example.com:1080 .
+#
+
+#
+# 6. WINDOWS GUI OPTIONS
+# ======================
+#
+# Privoxy has a number of options specific to the Windows GUI