-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML><HEAD><TITLE>Man page of PRIVOXY</TITLE>
-<LINK REL="STYLESHEET" TYPE="text/css" HREF="../p_doc.css"></HEAD><BODY>
-<H1>PRIVOXY</H1>
-Section: (1)<BR>Updated: 18 June 2008<BR><A HREF="#index">Index</A>
-<HR>
-
-<A NAME="lbAB"> </A>
-<H2>NAME</H2>
-
-privoxy - Privacy Enhancing Proxy
-<A NAME="lbAC"> </A>
-<H2>SYNOPSIS</H2>
-
-<P>
-<B>privoxy</B> [<B>--help</B> ] [<B>--version</B> ] [<B>--no-daemon</B> ] [<B>--pidfile </B><I>pidfile</I><B></B> ] [<B>--user </B><I>user[.group]</I><B></B> ] [<B>--chroot</B> ] [<B>--pre-chroot-nslookup </B><I>hostname</I><B></B> ] [<B></B><I>configfile</I><B></B> ]
-<P>
-<A NAME="lbAD"> </A>
-<H2>OPTIONS</H2>
-
-<P>
-
-<B>Privoxy</B> may be invoked with the following command line
-options:
-<DL COMPACT>
-<DT><B>--help</B><DD>
-Print brief usage info and exit.
-<DT><B>--version</B><DD>
-Print version info and exit.
-<DT><B>--no-daemon</B><DD>
-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.
-<DT><B>--pidfile </B><I>pidfile</I><B></B><DD>
-On startup, write the process ID to <I>pidfile</I>.
-Delete the <I>pidfile</I> on exit.
-Failure to create or delete the <I>pidfile</I>
-is non-fatal. If no <B>--pidfile</B> option is given, no PID file will be used.
-<DT><B>--user </B><I>user[.group]</I><B></B><DD>
-After (optionally) writing the PID file, assume the user ID of
-<I>user</I> and the GID of
-<I>group</I>, or, if the optional
-<I>group</I> was not given, the default group of
-<I>user</I>. Exit if the privileges are not
-sufficient to do so.
-<DT><B>--chroot</B><DD>
-Before changing to the user ID given in the --user option, chroot to
-that user's home directory, i.e. make the kernel pretend to the
-<B>Privoxy</B> process that the directory tree starts
-there. If set up carefully, this can limit the impact of possible
-vulnerabilities in <B>Privoxy</B> to the files contained in
-that hierarchy.
-<DT><B>--pre-chroot-nslookup </B><I>hostname</I><B></B><DD>
-Initialize the resolver library using <I>hostname</I>
-before chroot'ing. On some systems this reduces the number of files
-that must be copied into the chroot tree.
-</DL>
-<P>
-
-If the <I>configfile</I> is not specified on the command line,
-<B>Privoxy</B> will look for a file named
-<I>config</I> in the current directory . If no
-<I>configfile</I> is found, <B>Privoxy</B> will
-fail to start.
-<A NAME="lbAE"> </A>
-<H2>DESCRIPTION</H2>
-
-<P>
-
-Privoxy is a non-caching
-web proxy
-with advanced filtering capabilities for enhancing privacy,
-modifying web page data, managing HTTP
-cookies,
-controlling access, and removing ads, banners, pop-ups and other obnoxious
-Internet junk. Privoxy has a flexible configuration and can be
-customized to suit individual needs and tastes. Privoxy has application for
-both stand-alone systems and multi-user networks.
-<P>
-
-Privoxy is based on Internet Junkbuster (tm).
-<A NAME="lbAF"> </A>
-<H2>INSTALLATION AND USAGE</H2>
-
-<P>
-
-Browsers can either be individually configured to use
-<B>Privoxy</B> as a HTTP proxy (recommended),
-or <B>Privoxy</B> can be combined with a packet
-filter to build an intercepting proxy
-(see <I>config</I>). 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: <B>Edit</B>;
-<B>Preferences</B>; <B>Advanced</B>;
-<B>Proxies</B>; <B>Manual Proxy Configuration</B>;
-<B>View</B>.
-<P>
-
-For Firefox, go through: <B>Tools</B>;
-<B>Options</B>; <B>General</B>;
-<B>Connection Settings</B>;
-<B>Manual Proxy Configuration</B>.
-<P>
-
-For Internet Explorer, go through: <B>Tools</B>;
-<B>Internet Properties</B>; <B>Connections</B>;
-<B>LAN Settings</B>.
-<P>
-
-The Secure (SSL) Proxy should also be set to the same values, otherwise
-https: URLs will not be proxied. Note: <B>Privoxy</B> can only
-proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols.
-HTTPS presents some limitations, and not all features will work with HTTPS
-connections.
-<P>
-
-For other browsers, check the documentation.
-<A NAME="lbAG"> </A>
-<H2>CONFIGURATION</H2>
-
-<P>
-
-<B>Privoxy</B> can be configured with the various configuration
-files. The default configuration files are: <I>config</I>,
-<I>default.filter</I>, and
-<I>default.action</I>. <I>user.action</I> should
-be used for locally defined exceptions to the default rules of
-<I>default.action</I>, and <I>user.filter</I> for
-locally defined filters. These are well commented. On Unix
-and Unix-like systems, these are located in
-<I>/etc/privoxy/</I> by default.
-<P>
-
-<B>Privoxy</B> uses the concept of <B>actions</B>
-in order to manipulate the data stream between the browser and remote sites.
-There are various actions available with specific functions for such things
-as blocking web sites, managing cookies, etc. These actions can be invoked
-individually or combined, and used against individual URLs, or groups of URLs
-that can be defined using wildcards and regular expressions. The result is
-that the user has greatly enhanced control and freedom.
-<P>
-
-The actions list (ad blocks, etc) can also be configured with your
-web browser at <A HREF="http://config.privoxy.org/">http://config.privoxy.org/</A>
-(assuming the configuration allows it).
-<B>Privoxy's</B> configuration parameters can also be viewed at
-the same page. In addition, <B>Privoxy</B> can be toggled on/off.
-This is an internal page, and does not require Internet access.
-<P>
-
-See the <I>User Manual</I> for a detailed
-explanation of installation, general usage, all configuration options, new
-features and notes on upgrading.
-<A NAME="lbAH"> </A>
-<H2>SAMPLE CONFIGURATION</H2>
-
-<P>
-
-A brief example of what a simple <I>default.action</I>
-configuration might look like:
-<P>
-<PRE>
- # Define a few useful custom aliases for later use
- {{alias}}
-
- # Useful aliases that combine more than one action
- +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
- -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- +block-as-image = +block +handle-as-image
-
- # Fragile sites should have the minimum changes
- fragile = -block -deanimate-gifs -fast-redirects -filter \
- -hide-referer -prevent-cookies
-
- ## Turn some actions on ################################
- ## NOTE: Actions are off by default, unless explictily turned on
- ## otherwise with the '+' operator.
-
-{ \
-+deanimate-gifs{last} \
-+filter{refresh-tags} \
-+filter{img-reorder} \
-+filter{banners-by-size} \
-+filter{webbugs} \
-+filter{jumping-windows} \
-+filter{ie-exploits} \
-+hide-forwarded-for-headers \
-+hide-from-header{block} \
-+hide-referrer{conditional-block} \
-+session-cookies-only \
-+set-image-blocker{pattern} \
-}
-/ # '/' Match *all* URL patterns
-
-
- # Block all URLs that match these patterns
- { +block }
- ad.
- ad[sv].
- .*ads.
- banner?.
- /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
- .hitbox.com
- media./.*(ads|banner)
-
- # Block, and treat these URL patterns as if they were 'images'.
- # We would expect these to be ads.
- { +block-as-image }
- .ad.doubleclick.net
- .a[0-9].yimg.com/(?:(?!/i/).)*$
- ad.*.doubleclick.net
-
- # Make exceptions for these harmless ones that would be
- # caught by our +block patterns just above.
- { -block }
- adsl.
- adobe.
- advice.
- .*downloads.
- # uploads or downloads
- /.*loads
-</PRE>
-
-<P>
-
-Then for a <I>user.action</I>, we would put local,
-narrowly defined exceptions:
-<P>
-<PRE>
- # Re-define aliases as needed here
- {{alias}}
-
- # Useful aliases
- -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
-
- # Set personal exceptions to the policies in default.action #######
-
- # Sites where we want persistent cookies, so allow *all* cookies
- { -crunch-cookies -session-cookies-only }
- .redhat.com
- .sun.com
- .msdn.microsoft.com
-
- # These sites break easily. Use our "fragile" alias here.
- { fragile }
- .forbes.com
- mybank.example.com
-
- # Replace example.com's style sheet with one of my choosing
- { +redirect{<A HREF="http://localhost/css-replacements/example.com.css}">http://localhost/css-replacements/example.com.css}</A> }
- .example.com/stylesheet.css
-</PRE>
-
-<P>
-
-See the comments in the configuration files themselves, or the
-<I>User Manual</I>
-for full explanations of the above syntax, and other <B>Privoxy</B>
-configuration options.
-<A NAME="lbAI"> </A>
-<H2>FILES</H2>
-
-<P>
-<PRE>
-
- <I>/usr/sbin/privoxy</I>
- <I>/etc/privoxy/config</I>
- <I>/etc/privoxy/default.action</I>
- <I>/etc/privoxy/standard.action</I>
- <I>/etc/privoxy/user.action</I>
- <I>/etc/privoxy/default.filter</I>
- <I>/etc/privoxy/user.filter</I>
- <I>/etc/privoxy/trust</I>
- <I>/etc/privoxy/templates/*</I>
- <I>/var/log/privoxy/logfile</I>
-</PRE>
-
-<P>
-
-Various other files should be included, but may vary depending on platform
-and build configuration. Additional documentation should be included in the local
-documentation directory.
-<A NAME="lbAJ"> </A>
-<H2>SIGNALS</H2>
-
-<P>
-
-<B>Privoxy</B> terminates on the <B>SIGINT</B>,
-<B>SIGTERM</B> and <B>SIGABRT</B> signals. Log
-rotation scripts may cause a re-opening of the logfile by sending a
-<B>SIGHUP</B> to <B>Privoxy</B>. Note that unlike
-other daemons, <B>Privoxy</B> does not need to be made aware of
-config file changes by <B>SIGHUP</B> -- it will detect them
-automatically.
-<A NAME="lbAK"> </A>
-<H2>NOTES</H2>
-
-<P>
-
-This is a beta version of <B>Privoxy</B>. Not
-all features are well tested.
-<P>
-
-Please see the <I>User Manual</I> on how to contact the
-developers, for feature requests, reporting problems, and other questions.
-<A NAME="lbAL"> </A>
-<H2>SEE ALSO</H2>
-
-<P>
-
-Other references and sites of interest to <B>Privoxy</B>
-users:
-<P>
-
-<P>
-<A HREF="http://www.privoxy.org/">http://www.privoxy.org/,</A>
-the <B>Privoxy</B> Home page.
-<P>
-<A HREF="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/,</A>
-the <B>Privoxy</B> FAQ.
-<P>
-<A HREF="http://sourceforge.net/projects/ijbswa/">http://sourceforge.net/projects/ijbswa/,</A>
-the Project Page for <B>Privoxy</B> on
-SourceForge.
-<P>
-<A HREF="http://config.privoxy.org/">http://config.privoxy.org/,</A>
-the web-based user interface. <B>Privoxy</B> must be
-running for this to work. Shortcut: <A HREF="http://p.p/">http://p.p/</A>
-<P>
-<A HREF="http://sourceforge.net/tracker/?group_id=11118">http://sourceforge.net/tracker/?group_id=11118</A>&atid=460288, to submit ``misses'' and other
-configuration related suggestions to the developers.
-<P>
-<A HREF="http://www.junkbusters.com/ht/en/cookies.html">http://www.junkbusters.com/ht/en/cookies.html,</A>
-an explanation how cookies are used to track web users.
-<P>
-<A HREF="http://www.junkbusters.com/ijb.html">http://www.junkbusters.com/ijb.html,</A>
-the original Internet Junkbuster.
-<P>
-<A HREF="http://privacy.net/">http://privacy.net/,</A> a useful site
-to check what information about you is leaked while you browse the web.
-<P>
-<A HREF="http://www.squid-cache.org/">http://www.squid-cache.org/,</A> a popular
-caching proxy, which is often used together with <B>Privoxy</B>.
-<P>
-<A HREF="http://www.pps.jussieu.fr/~jch/software/polipo/">http://www.pps.jussieu.fr/~jch/software/polipo/,</A>
-<B>Polipo</B> is a caching proxy with advanced features
-like pipelining, multiplexing and caching of partial instances. In many setups
-it can be used as <B>Squid</B> replacement.
-<P>
-<A HREF="http://tor.eff.org/">http://tor.eff.org/,</A>
-<B>Tor</B> can help anonymize web browsing,
-web publishing, instant messaging, IRC, SSH, and other applications.
-<P>
-<A HREF="http://www.privoxy.org/developer-manual/">http://www.privoxy.org/developer-manual/,</A>
-the <B>Privoxy</B> developer manual.
-<A NAME="lbAM"> </A>
-<H2>DEVELOPMENT TEAM</H2>
-
-<P>
-<PRE>
- Fabian Keil, lead developer
- David Schmidt, developer
-
- Hal Burgiss
- Mark Miller
- Gerry Murphy
- Roland Rosenfeld
- Jörg Strohmayer
-</PRE>
-
-<A NAME="lbAN"> </A>
-<H2>COPYRIGHT AND LICENSE</H2>
-
-<A NAME="lbAO"> </A>
-<H3>COPYRIGHT</H3>
-
-<P>
-
-Copyright (C) 2001-2008 by Privoxy Developers <<A HREF="mailto:ijbswa-developers@lists.sourceforge.net">ijbswa-developers@lists.sourceforge.net</A>>
-<P>
-
-Some source code is based on code Copyright (C) 1997 by Anonymous Coders
-and Junkbusters, Inc. and licensed under the <I>GNU General Public
-License</I>.
-<A NAME="lbAP"> </A>
-<H3>LICENSE</H3>
-
-<P>
-
-<B>Privoxy</B> is free software; you can
-redistribute it and/or modify it under the terms of the
-<I>GNU General Public License</I>, version 2,
-as published by the Free Software Foundation.
-<P>
-
-This program is distributed in the hope that it will be useful, but WITHOUT
-ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE. See the <I>GNU General Public License</I> for details.
-<P>
-
-You should have received a copy of the <I>GNU GPL</I>
-along with this program; if not, write to the Free Software
-Foundation, Inc. 51 Franklin Street, Fifth Floor
-Boston, MA 02110-1301
-USA
-<P>
-
-<HR>
-<A NAME="index"> </A><H2>Index</H2>
-<DL>
-<DT><A HREF="#lbAB">NAME</A><DD>
-<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
-<DT><A HREF="#lbAD">OPTIONS</A><DD>
-<DT><A HREF="#lbAE">DESCRIPTION</A><DD>
-<DT><A HREF="#lbAF">INSTALLATION AND USAGE</A><DD>
-<DT><A HREF="#lbAG">CONFIGURATION</A><DD>
-<DT><A HREF="#lbAH">SAMPLE CONFIGURATION</A><DD>
-<DT><A HREF="#lbAI">FILES</A><DD>
-<DT><A HREF="#lbAJ">SIGNALS</A><DD>
-<DT><A HREF="#lbAK">NOTES</A><DD>
-<DT><A HREF="#lbAL">SEE ALSO</A><DD>
-<DT><A HREF="#lbAM">DEVELOPMENT TEAM</A><DD>
-<DT><A HREF="#lbAN">COPYRIGHT AND LICENSE</A><DD>
-<DL>
-<DT><A HREF="#lbAO">COPYRIGHT</A><DD>
-<DT><A HREF="#lbAP">LICENSE</A><DD>
-</DL>
-</DL>
-<HR>
-This document was created by
-man2html,
-using the manual pages.<BR>
-Time: 01:33:00 GMT, June 19, 2008
-</BODY>
-</HTML>
+<!-- Creator : groff version 1.19.2 -->
+<!-- CreationDate: Wed Jan 20 16:20:52 2021 -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <meta name="generator" content="groff -Thtml, see www.gnu.org">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <meta name="Content-Style" content="text/css">
+ <style type="text/css">
+ p { margin-top: 0; margin-bottom: 0; }
+ pre { margin-top: 0; margin-bottom: 0; }
+ table { margin-top: 0; margin-bottom: 0; }
+ </style>
+ <title>PRIVOXY</title>
+ <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
+</head>
+<body>
+ <h1 align="center">PRIVOXY</h1><a href="#NAME">NAME</a><br>
+ <a href="#SYNOPSIS">SYNOPSIS</a><br>
+ <a href="#OPTIONS">OPTIONS</a><br>
+ <a href="#DESCRIPTION">DESCRIPTION</a><br>
+ <a href="#INSTALLATION%20AND%20USAGE">INSTALLATION AND USAGE</a><br>
+ <a href="#CONFIGURATION">CONFIGURATION</a><br>
+ <a href="#FILES">FILES</a><br>
+ <a href="#SIGNALS">SIGNALS</a><br>
+ <a href="#NOTES">NOTES</a><br>
+ <a href="#SEE%20ALSO">SEE ALSO</a><br>
+ <a href="#DEVELOPMENT%20TEAM">DEVELOPMENT TEAM</a><br>
+ <a href="#COPYRIGHT%20AND%20LICENSE">COPYRIGHT AND LICENSE</a><br>
+ <hr>
+ <a name="NAME"></a>
+ <h2>NAME</h2>
+ <p style="margin-left:11%; margin-top: 1em">privoxy − Privacy Enhancing Proxy</p><a name="SYNOPSIS"></a>
+ <h2>SYNOPSIS</h2>
+ <p style="margin-left:11%; margin-top: 1em"><b>privoxy</b> [<b>−−chroot</b> ]
+ [<b>−−config-test</b> ] [<b>−−help</b> ] [<b>−−no-daemon</b> ]
+ [<b>−−pidfile</b> <i>pidfile</i> ] [<b>−−pre-chroot-nslookup</b> <i>hostname</i> ]
+ [<b>−−user</b> <i>user[.group]</i> ] [<b>−−version</b> ] [<i>configfile</i> ]</p><a name=
+ "OPTIONS"></a>
+ <h2>OPTIONS</h2>
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> may be invoked with the following command line options:
+ <b><br>
+ −−chroot</b></p>
+ <p style="margin-left:22%;">Before changing to the user ID given in the −−user option, chroot to that
+ user’s home directory, i.e. make the kernel pretend to the <b>Privoxy</b> process that the directory tree
+ starts there. If set up carefully, this can limit the impact of possible vulnerabilities in <b>Privoxy</b> to the
+ files contained in that hierarchy.</p>
+ <p style="margin-left:11%;"><b>−−config-test</b></p>
+ <p style="margin-left:22%;">Exit after loading the configuration files before binding to the listen address. The exit
+ code signals whether or not the configuration files have been successfully loaded.</p>
+ <p style="margin-left:22%; margin-top: 1em">If the exit code is 1, at least one of the configuration files is
+ invalid, if it is 0, all the configuration files have been successfully loaded (but may still contain errors that can
+ currently only be detected at run time).</p>
+ <p style="margin-left:22%; margin-top: 1em">This option doesn’t affect the log setting, combination with
+ "--no-daemon" is recommended if a configured log file shouldn’t be used.</p>
+ <table width="100%" border="0" rules="none" frame="void" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="9%">
+ <p style="margin-top: 1em" valign="top"><b>−−help</b></p>
+ </td>
+ <td width="2%"></td>
+ <td width="49%">
+ <p style="margin-top: 1em" valign="top">Print brief usage info and exit.</p>
+ </td>
+ <td width="29%"></td>
+ </tr>
+ </table>
+ <p style="margin-left:11%;"><b>−−no-daemon</b></p>
+ <p style="margin-left:22%;">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.</p>
+ <p style="margin-left:11%;"><b>−−pidfile</b> <i>pidfile</i></p>
+ <p style="margin-left:22%;">On startup, write the process ID to <i>pidfile</i>. Delete the <i>pidfile</i> on exit.
+ Failure to create or delete the <i>pidfile</i> is non-fatal. If no <b>−−pidfile</b> option is given, no
+ PID file will be used.</p>
+ <p style="margin-left:11%;"><b>−−pre-chroot-nslookup</b> <i>hostname</i></p>
+ <p style="margin-left:22%;">Initialize the resolver library using <i>hostname</i> before chroot’ing. On some
+ systems this reduces the number of files that must be copied into the chroot tree.</p>
+ <p style="margin-left:11%;"><b>−−user</b> <i>user[.group]</i></p>
+ <p style="margin-left:22%;">After (optionally) writing the PID file, assume the user ID of <i>user</i> and the GID of
+ <i>group</i>, or, if the optional <i>group</i> was not given, the default group of <i>user</i>. Exit if the
+ privileges are not sufficient to do so.</p>
+ <p style="margin-left:11%;"><b>−−version</b></p>
+ <p style="margin-left:22%;">Print version info and exit.</p>
+ <p style="margin-left:11%; margin-top: 1em">If the <i>configfile</i> is not specified on the command line,
+ <b>Privoxy</b> will look for a file named <i>config</i> in the current directory. If no <i>configfile</i> is found,
+ <b>Privoxy</b> will fail to start.</p><a name="DESCRIPTION"></a>
+ <h2>DESCRIPTION</h2>
+ <p style="margin-left:11%; margin-top: 1em">Privoxy is a non-caching web proxy with advanced filtering capabilities
+ for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other
+ obnoxious Internet junk. Privoxy has a flexible configuration and can be customized to suit individual needs and
+ tastes. It has application for both stand-alone systems and multi-user networks.</p>
+ <p style="margin-left:11%; margin-top: 1em">Privoxy is Free Software and licensed under the GNU GPLv2 or later.</p>
+ <p style="margin-left:11%; margin-top: 1em">Privoxy is an associated project of Software in the Public Interest
+ (SPI).</p>
+ <p style="margin-left:11%; margin-top: 1em">Helping hands and donations are welcome:</p>
+ <table width="100%" border="0" rules="none" frame="void" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="1%">
+ <p style="margin-top: 1em" valign="top">•</p>
+ </td>
+ <td width="2%"></td>
+ <td width="54%">
+ <p style="margin-top: 1em" valign="top">https://www.privoxy.org/participate</p>
+ </td>
+ <td width="32%"></td>
+ </tr>
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="1%">
+ <p style="margin-top: 1em" valign="top">•</p>
+ </td>
+ <td width="2%"></td>
+ <td width="54%">
+ <p style="margin-top: 1em" valign="top">https://www.privoxy.org/donate</p>
+ </td>
+ <td width="32%"></td>
+ </tr>
+ </table><a name="INSTALLATION AND USAGE"></a>
+ <h2>INSTALLATION AND USAGE</h2>
+ <p style="margin-left:11%; margin-top: 1em">Browsers can either be individually configured to use <b>Privoxy</b> as a
+ HTTP proxy (recommended), or <b>Privoxy</b> can be combined with a packet filter to build an intercepting proxy (see
+ <i>config</i>). The default setting is for localhost, on port 8118 (configurable in the main config file). To set the
+ HTTP proxy in Firefox, go through: <b>Tools</b>; <b>Options</b>; <b>General</b>; <b>Connection Settings</b>;
+ <b>Manual Proxy Configuration</b>.</p>
+ <p style="margin-left:11%; margin-top: 1em">For Internet Explorer, go through: <b>Tools</b>; <b>Internet
+ Properties</b>; <b>Connections</b>; <b>LAN Settings</b>.</p>
+ <p style="margin-left:11%; margin-top: 1em">The Secure (SSL) Proxy should also be set to the same values, otherwise
+ https: URLs will not be proxied. Note: <b>Privoxy</b> can only proxy HTTP and HTTPS traffic. Do not try it with FTP
+ or other protocols. HTTPS presents some limitations, and not all features will work with HTTPS connections.</p>
+ <p style="margin-left:11%; margin-top: 1em">For other browsers, check the documentation.</p><a name=
+ "CONFIGURATION"></a>
+ <h2>CONFIGURATION</h2>
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> can be configured with the various configuration files.
+ The default configuration files are: <i>config</i>, <i>default.filter</i>, <i>default.action</i> and
+ <i>default.action</i>. <i>user.action</i> should be used for locally defined exceptions to the default rules in
+ <i>match-all.action</i> and <i>default.action</i>, and <i>user.filter</i> for locally defined filters. These are well
+ commented. On Unix and Unix-like systems, these are located in <i>/etc/privoxy/</i> by default.</p>
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> uses the concept of <b>actions</b> in order to manipulate
+ the data stream between the browser and remote sites. There are various actions available with specific functions for
+ such things as blocking web sites, managing cookies, etc. These actions can be invoked individually or combined, and
+ used against individual URLs, or groups of URLs that can be defined using wildcards and regular expressions. The
+ result is that the user has greatly enhanced control and freedom.</p>
+ <p style="margin-left:11%; margin-top: 1em">The actions list (ad blocks, etc) can also be configured with your web
+ browser at http://config.privoxy.org/ (assuming the configuration allows it). <b>Privoxy’s</b> configuration
+ parameters can also be viewed at the same page. In addition, <b>Privoxy</b> can be toggled on/off. This is an
+ internal page, and does not require Internet access.</p>
+ <p style="margin-left:11%; margin-top: 1em">See the <i>User Manual</i> for a detailed explanation of installation,
+ general usage, all configuration options, new features and notes on upgrading.</p><a name="FILES"></a>
+ <h2>FILES</h2>
+ <p style="margin-left:11%; margin-top: 1em"><i>/usr/sbin/privoxy<br>
+ /etc/privoxy/config<br>
+ /etc/privoxy/match-all.action<br>
+ /etc/privoxy/default.action<br>
+ /etc/privoxy/user.action<br>
+ /etc/privoxy/default.filter<br>
+ /etc/privoxy/user.filter<br>
+ /etc/privoxy/trust<br>
+ /etc/privoxy/templates/*<br>
+ /var/log/privoxy/logfile</i></p>
+ <p style="margin-left:11%; margin-top: 1em">Various other files should be included, but may vary depending on
+ platform and build configuration. Additional documentation should be included in the local documentation
+ directory.</p><a name="SIGNALS"></a>
+ <h2>SIGNALS</h2>
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> terminates on the <b>SIGINT</b> and <b>SIGTERM</b>
+ signals. Log rotation scripts may cause a re-opening of the logfile by sending a <b>SIGHUP</b> to <b>Privoxy</b>.
+ Note that unlike other daemons, <b>Privoxy</b> does not need to be made aware of config file changes by <b>SIGHUP</b>
+ -- it will detect them automatically. Signals other than the ones listed above aren’t explicitly handled and
+ result in the default action defined by the operating system.</p><a name="NOTES"></a>
+ <h2>NOTES</h2>
+ <p style="margin-left:11%; margin-top: 1em">Please see the <i>User Manual</i> on how to contact the developers, for
+ feature requests, reporting problems, and other questions.</p><a name="SEE ALSO"></a>
+ <h2>SEE ALSO</h2>
+ <p style="margin-left:11%; margin-top: 1em">Other references and sites of interest to <b>Privoxy</b> users:</p>
+ <p style="margin-left:11%; margin-top: 1em">https://www.privoxy.org/, the <b>Privoxy</b> Home page.</p>
+ <p style="margin-left:11%; margin-top: 1em">https://www.privoxy.org/faq/, the <b>Privoxy</b> FAQ.</p>
+ <p style="margin-left:11%; margin-top: 1em">https://www.privoxy.org/developer-manual/, the <b>Privoxy</b> developer
+ manual.</p>
+ <p style="margin-left:11%; margin-top: 1em">https://sourceforge.net/projects/ijbswa/, the Project Page for
+ <b>Privoxy</b> on SourceForge.</p>
+ <p style="margin-left:11%; margin-top: 1em">http://config.privoxy.org/, the web-based user interface. <b>Privoxy</b>
+ must be running for this to work. Shortcut: http://p.p/</p>
+ <p style="margin-left:11%; margin-top: 1em">https://sourceforge.net/p/ijbswa/actionsfile-feedback/, to submit
+ ‘‘misses’’ and other configuration related suggestions to the developers.</p><a name=
+ "DEVELOPMENT TEAM"></a>
+ <h2>DEVELOPMENT TEAM</h2>
+ <p style="margin-left:11%; margin-top: 1em">Fabian Keil, lead developer<br>
+ David Schmidt<br>
+ Lee Rian<br>
+ Roland Rosenfeld<br>
+ Ian Silvester</p><a name="COPYRIGHT AND LICENSE"></a>
+ <h2>COPYRIGHT AND LICENSE</h2>
+ <p style="margin-left:11%; margin-top: 1em"><b>COPYRIGHT</b><br>
+ Copyright (C) 2001-2020 by Privoxy Developers <privoxy-devel@lists.privoxy.org></p>
+ <p style="margin-left:11%; margin-top: 1em">Some source code is based on code Copyright (C) 1997 by Anonymous Coders
+ and Junkbusters, Inc.</p>
+ <p style="margin-left:11%; margin-top: 1em"><b>LICENSE<br>
+ Privoxy</b> is free software; you can redistribute and/or modify its source code under the terms of the <i>GNU
+ General Public License</i> as published by the Free Software Foundation, either version 2 of the license, or (at your
+ option) any later version.</p>
+ <p style="margin-left:11%; margin-top: 1em">The same is true for <b>Privoxy</b> binaries unless they are linked with
+ a mbed TLS version that is licensed under the Apache 2.0 license in which case you can redistribute and/or modify the
+ <b>Privoxy</b> binaries under the terms of the <i>GNU General Public License</i> as published by the Free Software
+ Foundation, either version 3 of the license, or (at your option) any later version.</p>
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See
+ the <i>license</i> for details.</p>
+ <hr>
+</body>
+</html>
projects / privoxy.git / blobdiff