-# 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 to turn
-# off features: If you comment out the "logfile" line, junkbuster will
-# not log at all. Watch for the "default:" section in each explanation
-# to see what happens if the option is left unset (or commented out).
-#
-# Long lines can be continued on the next line by using a `\' as
-# the last character. This also works if comments are present in
-# between.
-#
-
-#
-# 3. OTHER CONFIGURATION FILES
-#
-# Junkbuster uses a number of other files to tell it what ads to
-# block, what cookies to accept, etc. This section of the
-# configuration file tells Junkbuster where to find all those other
-# files.
-#
-# On Windows, Junkbuster looks for these files in the same
-# directory as the executable. On Unix, Junkbuster looks for these
-# files in the current working directory. In either case, an
-# absolute path name can be used to avoid problems.
-
-#
-# The blockfile contains regular expressions, one per line, of URLs
-# to be blocked by Junkbuster.
-#
-# Default: Don't block anything.
-#
-blockfile ./blocklist
-
-#
-# The imagefile contains regular expressions, one per line, of URLs
-# to be blocked as images by Junkbuster, regardless of whether they
-# look like image URLs or not.
-#
-# Default: Block all URLs as HTML requests.
-#
-imagefile ./imagelist
-
-#
-# The permissions file contains patterns to specify the
-# cookie and filtering rules to apply to each site.
-#
-# Default: Cookies to and from all destinations are filtered.
-# Popups are disabled for all sites.
-# All sites are filtered if re_filterfile specified.
-#
-permissionsfile ./permissionsfile
-
-#
-# The re_filterfile contains content modification rules. These rules
-# permit powerful changes on the content of Web pages, e.g., you
-# could disable your favourite JavaScript annoyances, rewrite the
-# actual content, or just have some fun replacing "Microsoft"
-# with "Microsuck" wherever it appears on a Web page.
-#
-# Default: No content modification.
-#
-re_filterfile ./re_filterfile
-
-#
-# The logfile is where all logging and error messages are written.
-# The logfile can be useful for tracking down a problem with
-# Junkbuster (e.g., it's not blocking an ad you think it should
-# block) but in most cases you probably will never look at it.
-#
-# If you do not use 'log-buffer-size'/'log-max-lines' (see below)
-# 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').
-#
-# On SuSE Linux systems, you can place a line like
-# "/var/log/junkbuster.* +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.
-#
-# Default: Log to the standard error channel, not to a file
-#
-logfile ./junkbuster.log
-
-#
-# The jarfile defines where Junkbuster stores the cookies it
-# intercepts. Note that if you use a jarfile, it may grow quite
-# large.
-#
-# Default: Don't store intercepted cookies
-#
-#jarfile ./jarfile
-
-#
-# The forwardfile defines domain-specific forwarding of HTTP
-# requests. In some cases, you may want Junkbuster to forward your
-# request to another proxy instead of trying to fetch the request
-# itself. In those cases, you can use the forwardfile to indicate
-# which requests should be forwarded and to where.
-#
-# Default: Make all connections directly.
-#
-forwardfile ./forward
-
-#
-# Generally, Junkbuster is used as a personal proxy. The default
-# behaviour of Junkbuster is to listen on port 8000 on the "loopback"
-# interface, so that it will only listen to local requests from the
-# same machine. Using 'listen-address' (see below) you can serve
-# requests from other machines as well.
-#
-# In that case, it is a wise thing to define access control lists
-# (acls), which state who can connect to your proxy and what service
-# they will be given. Note that setting the listen-address to an IP
-# address that is only internally reachable from your local network
-# might already do the trick.
-#
-# Default: No access control. Everybody that can reach junkbuster
-# will be served.
-#
-#aclfile ./aclfile
-
-#
-# 4. OPTIONS
-#
-# This part of the configuration file contains options that control
-# how Junkbuster operates.
-#
-
-#
-# If 'add-forwarded-header' is set, an "X-Forwarded-For:"
-# specification will be added to each request header. Generally,
-# this is not needed and will reduce your privacy, as the server
-# will not only see which proxy the request came through, but also
-# which machine behind that proxy the request originally came from.
-#
-# Default: Don't add the "X-Forwarded-For:" header.
-#
-#add-forwarded-header
-
-#
-# Junkbuster can add "wafers", i.e. fake cookies, to each request
-# header it sends out.
-# These wafers can be seen by Web site operators in their log files,
-# so it's a way for you to communicate (very indirectly!) with
-# them. Junkbuster will add as many wafers as you like to each
-# request, just list them all here. Here's an example:
-#
-# wafer NOTE=Like most people, I want my browsing to be anonymous.
-# wafer WARNING=Please do not attempt to track me.
-#
-# Wafers make each request larger and will have a (small) impact on
-# your browsing speed, so you probably don't want to do this unless
-# you have a particular need.
-#
-# Default: Don't add a wafer
-#
-#wafer NOTE=Add your wafer here...
-
-#
-# There's also a pre-defined wafer containing a privacy message,
-# called the vanilla wafer, which is sent by default. Setting
-# suppress-vanilla-wafer suppresses this. You guessed that, didn't you?
-#
-# Default: Send the vanilla wafer
-#
-suppress-vanilla-wafer
-
-#
-# In fact, Junkbuster can add anything at all to the request headers.
-# You can specify the headers to add with the add-header option. For
-# example:
-#
-# add-header Forwarded: by http://stay-out-of-my-backyard.net
-#
-# Generally, random headers will simply be ignored by the Web site,
-# so there's little use in adding them. However, there are some
-# cases where you might want to add a header, e.g., if you're
-# forwarding Junkbuster requests to another proxy you might want to
-# add:
-#
-# add-header Proxy-Connection: Keep-Alive
-#
-# to every request.
-#
-#add-header My-Header: Whatever you'd like...
-
-#
-# Listen-address specifies the address and port where Junkbuster will
-# listen for connections from your Web browser. The default is to
-# listen on the local host on port 8000, and this is suitable for
-# most users. (In your web browser, under proxy configuration, list
-# the proxy server as 'localhost' and the port as '8000').
-#
-# If you already have another service running on port 8000, 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. The syntax
-# is "listen-address [<ip-address>]:<port>" If you leave out the ip
-# adress, junkbuster 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 "aclfile" above).
-#
-# For example, suppose you are running Junkbuster 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:8000
-#
-# If you want it to listen on all addresses (including the outside
-# connection):
-#
-# listen-address :8000
-#
-# If you do this, consider using acls (see "aclfile" above).
-#
-# Note: you will need to point your browser(s) to the address
-# and port that you have configured here.
-#
-# Default: listen-address localhost:8000
-# listen-address 127.0.0.1:8000
-#
-
-#
-# When your Web browser makes a request from a Web site, it informs
-# the Web site what sort of browser it is, e.g., "Internet Explorer
-# V2.0" or some such. In theory, Web sites can use this information
-# to tailor themselves for your browser.
-#
-# The 'user-agent' option controls whether Junkbuster will conceal
-# your browser type or not. If user-agent is set to . (period) the
-# User-Agent header is passed to the server unchanged, along with any
-# UA headers produced by MS-IE (which would otherwise be deleted). If
-# user-agent is set to @ (at) these headers are sent unchanged in
-# cases where the cookiefile specifies that a cookie would be sent,
-# otherwise only a default User-Agent header is sent. That default is
-# Mozilla/3.0 (Netscape) with an unremarkable Linux configuration.
-# If left unset, the default header is always sent.
-#
-# Note that if you choose to mislead Web sites about your browser
-# type, you may get Web pages that confuse your browser or display
-# incorrectly. In most cases, it's probably fine to send your real
-# browser type.
-#
-# Default: Always send the (forged) default user agent header
-#
-user-agent .
-
-#
-# When your Web browser requests a page from a Web site, it also
-# informs the Web site where it came from, i.e., when you click
-# through to a new web page, your browser tells the new web site the
-# URL of the old web page. This is called the "Referer" header.
-#
-# Junkbuster has the ability to mask the Referer header. Referer
-# headers can be used to track users as they browse around the web,
-# and many consider them invasive. Junkbuster provides several
-# options for dealing with referer headers:
-#
-# VALUE EFFECT
-# ===== ======
-# default Kill the referrer-header from the client.
-# . Pass the referrer unchanged.
-# @ Pass the referrer if the server is in the cookie file,
-# kill the referrer otherwise.
-# L Pass the referrer if the server is in the cookie file,
-# send a forged referrer that points to the
-# root-directory URL of the current request otherwise.
-# 'text' Always send <text> as the referrer.
-#
-# L is probably preferable to @, because it will break fewer Web
-# sites while still concealing your browsing path.
-#
-# Default: see above
-#
-referer L
-
-#
-# Some browsers provide a "From:" header that gives Web sites your
-# email address. The only real effect of this is to make you a
-# target for unsolicited email (spam). There are three options
-# what to do with the "From:" header if it is present:
-#
-# VALUE EFFECT
-# ===== ======
-# default Kill every "From:" header
-# . Pass the "From:" header unchanged
-# 'text' replace the email address in the "From:" header with 'text'
-#
-# Default: see above
-#
-#from spam-me-senseless@sittingduck.xqq
-
-#
-# The 'tinygif' option lets you change how Junkbuster treats blocked
-# images. The default behavior is to send an HTML answer to requests
-# for images, resulting in a "broken image icon" in place of the blocked
-# image. That's a little ugly, so several other options are available:
-#
-# VALUE EFFECT
-# ===== ======
-# 0 Send HTML
-# 1 Send a GIF of one transparent pixel
-# 2 Send a GIF with the word "JUNKBUSTER"
-# 3 <url> Send a redirect to the image indicated by the <url>
-#
-# As an example of the last option:
-#
-# tinygif 3 http://no.where/ijb-send-banner.gif
-#
-# Will replace every blocked image with an image built into junkbuster.
-#
-# There is one non-obvious benefit to using option "3". If you use
-# option 3, your Web browser will likely cache the image you specify
-# on your local machine. That means that after the first use, that
-# image will load very quickly (and won't require a request to the
-# junkbuster proxy)
-#
-# Default: 0, i.e. send HTML
-#
-tinygif 2
-
-#
-# Many sites, like yahoo.com, don't just link to other sites.
-# Instead, they will link to some script on their own server,
-# giving the destination as a parameter, which will then redirect
-# you to the final target.
-#
-# URLs resulting from this scheme typically look like:
-# http://some.place/some_script?http://some.where-else
-#
-# Sometimes, there are even multiple consecutive redirects encoded
-# in the URL. These redirections via scripts make your web browing
-# more traceable, since the server from which you follow such a link
-# can see where you go to. Apart from that, valuable bandwidth and
-# time is wasted, while your browser aks the server for one redirect
-# after the other. Plus, it feeds the advertisers.
-#
-# The fast-redirects option enables interception of these requests
-# by junkbuster, who will cut off all but the last valid URL in the
-# request and send a local redirect back to your browser without
-# contacting the remote site.
-#
-# Default: Don't intercept script-redirect URLs
-#
-fast-redirects
-
-#
-# The debug option sets the level of debugging information to log in
-# the logfile (and to the console in the Windows version). A debug
-# level of 1 is informative because it will show you each request as
-# it happens. Higher levels of debug are probably only of interest
-# to developers.
-#
-# 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
-# debug 128 # RED = debug fast redirects
-#
-# Multiple "debug" directives, are OK - they're logical-OR'd
-# together.
-#
-# debug 15 # same as setting the first 4 listed above
-#
-# Default: 0, i.e. log nothing but errors and infos
-#
-debug 1
-
-#
-# Junkbuster normally uses "multi-threading", a software technique
-# that permits it to handle many different requests simultaneously.
-# In some cases you may wish to disable this -- particularly if
-# you're trying to debug a problem. The 'single-threaded' option
-# forces Junkbuster to handle requests sequentially.
-#
-# Default: Multithreaded mode
-#
+# 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.
+#