-# Sample Configuration File for Privoxy v3.0.12
+# Sample Configuration File for Privoxy v3.0.13
#
-# $Id: config,v 1.76 2009/03/21 11:51:51 fabiankeil Exp $
+# $Id: p-config.sgml,v 2.48 2009/04/17 11:42:07 fabiankeil Exp $
#
# Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
#
# 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
+# request as it happens. 1, 1024, 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
#
# 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.
+# Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is suitable
+# and recommended for home users who run Privoxy on the same
+# machine as their browser.
#
# Notes:
#
# 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
+# IPv6 addresses containing colons have to be quoted by brackets.
+#
+# If you leave out the IP address, Privoxy will bind to all IPv4
# 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.
+# lists (ACL's, see below), and/or a firewall. If the hostname
+# is localhost, Privoxy will explicitly try to bind to an IPv4
+# address. For other hostnames it depends on the operating system
+# which IP version will be used.
#
# If you open Privoxy to untrusted users, you will also
# want to make sure that the following actions are disabled:
# listen-address 192.168.0.1:8118
#
#
+# Suppose you are running Privoxy on an IPv6-capable machine and
+# you want it to listen on the IPv6 address of the loopback device:
+#
+# listen-address [::1]:8118
+#
+#
listen-address 127.0.0.1:8118
#
#
#
# Type of value:
#
-# src_addr[/src_masklen] [dst_addr[/dst_masklen]]
+# src_addr[:port][/src_masklen] [dst_addr[:port][/dst_masklen]]
+#
+# Where src_addr and dst_addr are IPv4 addresses in dotted
+# decimal notation or valid DNS names, port is a port number, 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.
#
-# 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.
+# If your system implements RFC 3493, then src_addr and dst_addr
+# can be IPv6 addresses delimeted by brackets, port can be a
+# number or a service name, and src_masklen and dst_masklen can
+# be a number from 0 to 128.
#
# Default value:
#
# Unset
#
+# If no port is specified, any port will match. If no src_masklen
+# or src_masklen is given, the complete IP address has to match
+# (i.e. 32 bits for IPv4 and 128 bits for IPv6).
+#
# Effect if unset:
#
# Don't restrict access further than implied by listen-address
# names. If a DNS name resolves to multiple IP addresses, only
# the first one is used.
#
+# Some systems allows IPv4 client to connect to IPv6 server
+# socket. Then the client's IPv4 address will be translated by
+# system into IPv6 address space with special prefix ::ffff:0:0/96
+# (so called IPv4 mapped IPv6 address). Privoxy can handle it
+# and maps such ACL addresses automatically.
+#
# 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 (most sites are).
# permit-access 192.168.45.64/26
# deny-access 192.168.45.73 www.dirty-stuff.example.com
#
+# Allow access from the IPv4 network 192.0.2.0/24 even if listening
+# on an IPv6 wild card address (not supported on all platforms):
+#
+# permit-access 192.0.2.0/24
+#
+#
+# This is equivalent to the following line even if listening on
+# an IPv4 address (not supported on all platforms):
+#
+# permit-access [::ffff:192.0.2.0]/120
#
#
# 4.8. buffer-limit
# 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: 8000). Use a single dot (.) to denote "no forwarding".
#
# Default value:
#
# If http_parent is ".", then requests are not forwarded to
# another HTTP proxy but are made directly to the web servers.
#
+# http_parent can be a numerical IPv6 address (if RFC 3493 is
+# implemented). To prevent clashes with the port delimiter,
+# the whole IP address has to be put into brackets. On the other
+# hand a target_pattern containing an IPv6 address has to be put
+# into angle brackets (normal brackets are reserved for regular
+# expressions already).
+#
# Multiple lines are OK, they are checked in sequence, and the
# last match wins.
#
# forward .isp.example.net .
#
#
+# Parent proxy specified by an IPv6 address:
+#
+# foward / [2001:DB8::1]:8000
+#
+#
+# Suppose your parent proxy doesn't support IPv6:
+#
+# forward / parent-proxy.example.org:8000
+# forward ipv6-server.example.org .
+# forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> .
#
#
# 5.2. forward-socks4, forward-socks4a and forward-socks5
# With forward-socks5 the DNS resolution will happen on the remote
# server as well.
#
+# socks_proxy and http_parent can be a numerical IPv6 address
+# (if RFC 3493 is implemented). To prevent clashes with the port
+# delimiter, the whole IP address has to be put into brackets. On
+# the other hand a target_pattern containing an IPv6 address has
+# to be put into angle brackets (normal brackets are reserved
+# for regular expressions already).
+#
# 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.