X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=config;h=4fa0a3712fce1e92a1ef3b341f9ae9b0bd0107b3;hp=88529d013fde08dd9d6e1961548a9c1e63737eec;hb=410a819a57f1deee21703f1cb0dd18b707a7adaa;hpb=12f52e6af55d51d4b268af7956d97c772eebbb5c diff --git a/config b/config index 88529d01..4fa0a371 100644 --- a/config +++ b/config @@ -1,7 +1,7 @@ # Sample Configuration file for the Internet Junkbuster 2.0 # -# $Id: config,v 1.6 2001/05/26 17:25:14 jongfoster Exp $ +# $Id: config,v 1.12 2001/06/04 10:44:57 swa Exp $ # # Table of Contents @@ -61,7 +61,25 @@ # files in the current working directory. In either case, an # absolute path name can be used to avoid problems. +# While we go modular and multiuser, the blocker, filter, and +# per-user config will be stored in subdirectories of confdir. +# Now, only confdir/templates is used for storing HTML templates +# for CGI results. # +# No trailing /, please. +confdir . + +# +# The directory where all logging (i.e. logfile and jarfile) takes place +# No trailing /, please. +# +logdir . + +# +# Note that all file specifications below are relative to +# the above two directories!!! +# + # The permissions file contains patterns to specify the # filtering rules to apply to each site. # @@ -70,7 +88,7 @@ # All sites are filtered if re_filterfile specified. # No sites are blocked. Nothing is an image. # -permissionsfile ./permissionsfile +permissionsfile permissionsfile # # The re_filterfile contains content modification rules. These rules @@ -81,7 +99,7 @@ permissionsfile ./permissionsfile # # Default: No content modification. # -re_filterfile ./re_filterfile +re_filterfile re_filterfile # # The logfile is where all logging and error messages are written. @@ -100,7 +118,7 @@ re_filterfile ./re_filterfile # # Default: Log to the standard error channel, not to a file # -logfile ./junkbuster.log +logfile logfile # # The jarfile defines where Junkbuster stores the cookies it @@ -109,7 +127,7 @@ logfile ./junkbuster.log # # Default: Don't store intercepted cookies # -#jarfile ./jarfile +#jarfile jarfile # # The forwardfile defines domain-specific forwarding of HTTP @@ -120,7 +138,7 @@ logfile ./junkbuster.log # # Default: Make all connections directly. # -forwardfile ./forward +forwardfile forward # # Generally, Junkbuster is used as a personal proxy. The default @@ -138,7 +156,7 @@ forwardfile ./forward # Default: No access control. Everybody that can reach junkbuster # will be served. # -#aclfile ./aclfile +#aclfile aclfile # # 4. OPTIONS @@ -147,64 +165,6 @@ forwardfile ./forward # 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 @@ -241,109 +201,6 @@ suppress-vanilla-wafer # 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. -# -# Note that the setting of this value can be overridden on a -# site-by-site basis in the permissionsfile, in order to send -# the unmodified Referer header to sites which require it. -# This option controls what to do for sites without that -# permission. -# -# VALUE EFFECT -# ===== ====== -# default Kill the referrer-header from the client. -# @ Kill the referrer-header from the client. -# . Always pass the referrer unchanged. -# L Send a forged referrer that points to the -# root-directory URL of the current request otherwise. -# 'text' Send 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 Send a redirect to the image indicated by the -# -# As an example of the last option: -# -# tinygif 3 http://i.j.b/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 - # # The debug option sets the level of debugging information to log in @@ -380,7 +237,8 @@ tinygif 2 # # Default: 0, i.e. log nothing but fatal errors # -debug 1 +debug 1 # URLs +debug 4096 # Info debug 8192 # Errors - *we highly recommended enabling this* #