]> 2002-04-11 privoxy 1 Privoxy &p-version; privoxy Privacy Enhancing Proxy privoxy --help --version --no-daemon --pidfile pidfile --user user[.group] configfile (UNIX) privoxy.exe configfile (Windows) Privoxy may be invoked with the following command line options: --help Print brief usage info and exit. --version Print version info and exit. --no-daemon Don't become a daemon, i.e. don't fork and become process group leader, don't detach from controlling tty, and do all logging there. --pidfile pidfile On startup, write the process ID to pidfile. Delete the pidfile on exit. Failiure to create or delete the pidfile is non-fatal. If no --pidfile option is given, no PID file will be used. --user user[.group] After (optionally) writing the PID file, assume the user ID of user and the GID of group, or, if the optional group was not given, the default group of user. Exit if the privileges are not sufficient to do so. If the configfile is not specified on the command line, Privoxy will look for a file named config in the current directory (except on Win32 where it will try config.txt). If no configfile is found, Privoxy will fail to start. &p-intro; Browsers must be individually configured to use Privoxy as a HTTP proxy. The default setting is for localhost, on port 8118 (configurable in the main config file). To set the HTTP proxy in Netscape and Mozilla, go through: Edit; Preferences; Advanced; Proxies; Manual Proxy Configuration; View. For Internet Explorer, go through: Tools; Internet Properties; Connections; LAN Settings. The Secure (SSL) Proxy should also be set to the same values, otherwise https: URLs will not be proxied. For other browsers, check the documentation. Privoxy can be configured with the various configuration files. The default configuration files are: config, default.action, and default.filter. These are well commented. On Unix and Unix-like systems, these are located in /etc/privoxy/ by default. On Windows, OS/2 and AmigaOS, these files are in the same directory as the Privoxy executable. The name and number of configuration files has changed from previous versions, and is subject to change as development progresses. In fact, the configuration itself is changed and much more sophisticated. See the user-manual for a brief explanation of all configuration options. The actions list (ad blocks, etc) can also be configured with your web browser at http://ijbswa.sourceforge.net/config. Privoxy's configuration parameters can also be viewed at the same page. In addition, Privoxy can be toggled on/off. This is an internal page. A brief example of what a default.action configuration might look like: # Define a few useful custom aliases for later use {{alias}} # Don't accept cookies +no-cookies = +no-cookies-set +no-cookies-read # Do accept cookies -no-cookies = -no-cookies-set -no-cookies-read # Treat these blocked URLs as images. +imageblock = +block +image # Define page filters we want to use. myfilters = +filter{html-annoyances} +filter{js-annoyances}\ +filter{no-popups} +filter{webbugs} ## Default Policies (actions) ############################ { \ -block \ -downgrade \ +fast-redirects \ myfilters \ +no-compression \ +hide-forwarded \ +hide-from{block} \ +hide-referer{forge} \ -hide-user-agent \ -image \ +image-blocker{blank} \ +no-cookies-keep \ -no-cookies-read \ -no-cookies-set \ +no-popups \ -vanilla-wafer \ -wafer \ } / # Now set exceptions to the above defined policies ####### # Sites where we want persistant cookies {-no-cookies -no-cookies-keep} .redhat.com .sun.com .yahoo.com .msdn.microsoft.com # This site requires cookies AND 'fast-redirects' on {-no-cookies -no-cookies-keep -fast-redirects} .nytimes.com # Add custom headers, and turn off filtering of page source {+add-header{X-Privacy: Yes please} #-add-header{*} \ +add-header{X-User-Tracking: No thanks!} -filter} privacy.net # Block, and treat these URLs as 'images'. {+imageblock} .adforce.imgis.com .ad.preferences.com/image.* .ads.web.aol.com .ad-adex3.flycast.com .ad.doubleclick.net .ln.doubleclick.net .ad.de.doubleclick.net /.*/count\.cgi\?.*df= 194.221.183.22[1-7] a196.g.akamai.net/7/196/2670/000[12]/images.gmx.net/i4/images/.*/ # Block any URLs that match these patterns {+block} /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g)) /.*/(plain|live|rotate)[-_.]?ads?/ /.*/(sponsor)s?[0-9]?/ /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe) /.*/adbanners/ /.*/adv((er)?ts?|ertis(ing|ements?))?/ /.*/banners?/ /.*/popupads/ /.*/advert[0-9]+\.jpg /ad_images/ /.*/ads/ /images/.*/.*_anim\.gif /rotations/ /.*(ms)?backoff(ice)?.*\.(gif|jpe?g) 195.63.104.*/(inbox|log|meld|folderlu|folderru|log(in|out)[lmr]u|) .images.nytimes.com .images.yahoo.com/adv/ /.*cnnstore\.gif See the comments in the configuration files themselves, or the user-manual for explanations of the above syntax, and other Privoxy configuration options. /usr/sbin/privoxy /etc/privoxy/config /etc/privoxy/default.action /etc/privoxy/advanced.action /etc/privoxy/basic.action /etc/privoxy/intermediate.action /etc/privoxy/default.filter /etc/privoxy/trust /etc/privoxy/templates/* /var/log/privoxy/logfile Various other files should be included, but may vary depending on platform and build configuration. More documentation should be included in the local documentation directory, though is not complete at this time. Privoxy terminates on the SIGINT, SIGTERM and SIGABRT signals. Log rotation scripts may cause a re-opening of the logfile by sending a SIGHUP to Privoxy. Note that unlike other daemons, Privoxy does not need to be made aware of config file changes by SIGHUP -- it will detect them automatically. This is a &p-status; version of Privoxy. Not all features are well tested. ]]> Please see the user-manual on how to contact the developers for feature requests, reporting problems, and other questions. &seealso; &authors; ©right;