-# Sample Configuration File for Privoxy v3.1.1
+# Sample Configuration File for Privoxy v3.0.x
#
-# Copyright (C) 2001, 2002 Privoxy Developers http://privoxy.org
+# Copyright (C) 2001-2004 Privoxy Developers http://privoxy.org
#
-# $Id: config,v 1.41 2002/10/09 01:45:33 hal9 Exp $
+# $Id: config,v 1.49 2006/08/12 04:03:40 david__schmidt Exp $
#
####################################################################
# #
#
# Specifies:
#
-# The filter file to use
+# The filter file(s) to use
#
# Type of value:
#
#
# Notes:
#
-# The filter file contains content modification rules that use
+# The filter files contain 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.
+# or just have some fun playing buzzword bingo with a web page.
#
# The +filter{name} actions rely on the relevant filter (name)
-# to be defined in the filter file!
+# to be defined in a 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.
-#
+# When adding your own, it is recommended you add them to the
+# user.filter file.
+#
filterfile default.filter
+#filterfile user.filter
#
# 1.5. logfile
#
# Default value:
#
-# jarfile (Unix) or privoxy.jar (Windows)
+# Unset (commented out). When activated: jarfile (Unix)
+# or privoxy.jar (Windows)
#
# Effect if unset:
#
-# Intercepted cookies are not stored at all.
+# Intercepted cookies are not stored in a dedicated file.
#
# Notes:
#
# The jarfile may grow to ridiculous sizes over time.
+#
+# If debug 8 (show header parsing) is enabled, cookies are
+# written to the logfile with the rest of the headers.
#
-jarfile jarfile
+#jarfile jarfile
#
# 1.7. trustfile
#
# Unix, in local filesystem:
#
-# user-manual file:///usr/share/doc/privoxy-2.9.18/user-manual/
+# user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/index.html
+#
+# Windows, in local filesystem, must use forward slash notation,
+# and %20 to denote spaces in path names:
+#
+# user-manual file:///c:/some%20dir/privoxy/user-manual/index.html
+#
+# Windows, UNC notation (forward slashes required again):
+#
+# user-manual file://///some-server/some-path/privoxy/user-manual/index.html
#
# Any platform, on local webserver (called "local-webserver"):
#
-# user-manual http://local-webserver/privoxy-user-manual/
+# user-manual http://local-webserver/privoxy-user-manual/
#
# WARNING!!!
#
# HTTP parent looks like this:
#
# forward-socks4 / socks-gw.example.com:1080 .
+#
+# To chain Privoxy and Tor, both running on the same system,
+# you should use the rule:
#
+# forward-socks4a / 127.0.0.1:9050 .
+#
+# The public Tor network can't be used to reach your local network,
+# therefore it's a good idea to make some exceptions:
+#
+# forward 192.168.*.*/ .
+# forward 10.*.*.*/ .
+# forward 127.*.*.*/ .
+#
+# Unencrypted connections to systems in these address ranges will
+# be as (un)secure as the local network is, but the alternative is
+# that you can't reach the network at all.
+#
+# If you also want to be able to reach servers in your local
+# network by using their names, you will need additional
+# exceptions that look like this:
+#
+# forward localhost/ .
#
# 6. WINDOWS GUI OPTIONS
#
#hide-console
-# The experimental "activity-console-address" option is used to
-# specify where statistical information should be sent for monitoring
-# by the activity console.
-#
-#activity-console-address 127.0.0.1:8119
-
-# The experimental "activity-console-update-freq" option is used to
-# specify how often (in seconds) statistics should be forwarded to the
-# activity console.
-#
-#activity-console-update-freq 5
-
#
projects / privoxy.git / blobdiff