because a person can read code does not mean they will understand why
or what is being done. A reader may spend a lot more time figuring
out what is going on when a simple comment or explanation would have
- prevented the extra research. Please help your brother IJB'ers
- out!</p>
+ prevented the extra research. Please help your fellow Privoxy
+ developers out!</p>
<p>The comments will also help justify the intent of the code. If the
comment describes something different than what the code is doing
<td>
<pre class="PROGRAMLISTING">
/* if page size greater than 1k ... */
-if ( page_length() > 1024 )
+if (page_length() > 1024)
{
... "block" the page up ...
}
/* if page size is small, send it in blocks */
-if ( page_length() > 1024 )
+if (page_length() > 1024)
{
... "block" the page up ...
}
/*********************************************************************
* This will stand out clearly in your code!
*********************************************************************/
-if ( this_variable == that_variable )
+if (this_variable == that_variable)
{
do_something_very_important();
}
/* unfortunately, this may not */
-if ( this_variable == that_variable )
+if (this_variable == that_variable)
{
do_something_very_important();
}
-if ( this_variable == that_variable ) /* this may not either */
+if (this_variable == that_variable) /* this may not either */
{
do_something_very_important();
}
* This will stand out clearly in your code,
* But the second example won't.
*********************************************************************/
-if ( this_variable == this_variable )
+if (this_variable == this_variable)
{
do_something_very_important();
}
-if ( this_variable == this_variable ) /*can you see me?*/
+if (this_variable == this_variable) /*can you see me?*/
{
do_something_very_important(); /*not easily*/
}
int urls_read = 0; /* # of urls read + rejected */
int urls_rejected = 0; /* # of urls rejected */
-if ( 1 == X )
+if (1 == X)
{
do_something_very_important();
}
<tr>
<td>
<pre class="PROGRAMLISTING">
-if ( 1 == X )
+if (1 == X)
{
do_something_very_important();
...some long list of commands...
or:
-if ( 1 == X )
+if (1 == X)
{
do_something_very_important();
...some long list of commands...
-} /* -END- if ( 1 == X ) */
+} /* -END- if (1 == X) */
</pre>
</td>
</tr>
<tr>
<td>
<pre class="PROGRAMLISTING">
-int load_some_file( struct client_state *csp )
+int load_some_file(struct client_state *csp)
</pre>
</td>
</tr>
<tr>
<td>
<pre class="PROGRAMLISTING">
-int loadsomefile( struct client_state *csp )
-int loadSomeFile( struct client_state *csp )
+int loadsomefile(struct client_state *csp)
+int loadSomeFile(struct client_state *csp)
</pre>
</td>
</tr>
<tr>
<td>
<pre class="PROGRAMLISTING">
-(.h) extern int load_aclfile( struct client_state *csp );
-(.c) int load_aclfile( struct client_state *csp )
+(.h) extern int load_aclfile(struct client_state *csp);
+(.c) int load_aclfile(struct client_state *csp)
</pre>
</td>
</tr>
<tr>
<td>
<pre class="PROGRAMLISTING">
-(.h) extern int load_aclfile( struct client_state * ); or
+(.h) extern int load_aclfile(struct client_state *); or
(.h) extern int load_aclfile();
-(.c) int load_aclfile( struct client_state *csp )
+(.c) int load_aclfile(struct client_state *csp)
</pre>
</td>
</tr>
<tr>
<td>
<pre class="PROGRAMLISTING">
-(enumeration) : enum Boolean { FALSE, TRUE };
+(enumeration) : enum Boolean {FALSE, TRUE};
(#define) : #define DEFAULT_SIZE 100;
</pre>
</td>
<tr>
<td>
<pre class="PROGRAMLISTING">
-if ( this == that )
+if (this == that)
{
...
}
<p><span class="emphasis"><i class="EMPHASIS">Instead
of:</i></span></p>
- <p>if ( this == that ) { ... }</p>
+ <p>if (this == that) { ... }</p>
<p>or</p>
- <p>if ( this == that ) { ... }</p>
+ <p>if (this == that) { ... }</p>
<p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> In the
special case that the if-statement is inside a loop, and it is
<tr>
<td>
<pre class="PROGRAMLISTING">
-while ( more lines are read )
+while (more lines are read)
{
/* Please document what is/is not a comment line here */
- if ( it's a comment ) continue;
+ if (it's a comment) continue;
- do_something( line );
+ do_something(line);
}
</pre>
</td>
<tr>
<td>
<pre class="PROGRAMLISTING">
-if ( this == that )
+if (this == that)
{
do_something();
do_something_else();
<p><span class="emphasis"><i class="EMPHASIS">Instead
of:</i></span></p>
- <p>if ( this == that ) do_something(); do_something_else();</p>
+ <p>if (this == that) do_something(); do_something_else();</p>
<p>or</p>
- <p>if ( this == that ) do_something();</p>
+ <p>if (this == that) do_something();</p>
<p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> The
first example in "Instead of" will execute in a manner other than
<tr>
<td>
<pre class="PROGRAMLISTING">
-structure->flag = ( condition );
+structure->flag = (condition);
</pre>
</td>
</tr>
<p><span class="emphasis"><i class="EMPHASIS">Instead
of:</i></span></p>
- <p>if ( condition ) { structure->flag = 1; } else {
+ <p>if (condition) { structure->flag = 1; } else {
structure->flag = 0; }</p>
<p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> The
int some_value = 0;
int another_value = 0;
int this_variable = 0;
-
-if ( this_variable == this_variable )
-
-first_value = old_value + ( ( some_value - another_value ) - whatever )
</pre>
</td>
</tr>
int function1( ... )
{
...code...
- return( ret_code );
+ return(ret_code);
-} /* -END- function1 */
+} /* -END- function1 */
int function2( ... )
{
-} /* -END- function2 */
+} /* -END- function2 */
</pre>
</td>
</tr>
<p><span class="emphasis"><i class="EMPHASIS">Instead
of:</i></span></p>
- <p>int function1( ... ) { ...code... return( ret_code ); } int
+ <p>int function1( ... ) { ...code... return(ret_code); } int
function2( ... ) { }</p>
<p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> Use 1
int function1( ... )
{
- if ( 1 )
+ if (1)
{
- return( ALWAYS_TRUE );
+ return ALWAYS_TRUE;
}
else
{
- return( HOW_DID_YOU_GET_HERE );
+ return HOW_DID_YOU_GET_HERE;
}
- return( NEVER_GETS_HERE );
+ return NEVER_GETS_HERE;
}
</pre>
<tr>
<td>
<pre class="PROGRAMLISTING">
-for ( size_t cnt = 0; cnt < block_list_length(); cnt++ )
+for (size_t cnt = 0; cnt < block_list_length(); cnt++)
{
....
}
<pre class="PROGRAMLISTING">
size_t len = block_list_length();
-for ( size_t cnt = 0; cnt < len; cnt++ )
+for (size_t cnt = 0; cnt < len; cnt++)
{
....
}
<p>This allows a developer to define a const pointer and call your
function. If your function does not have the const keyword, we may
not be able to use your function. Consider strcmp, if it were defined
- as: extern int strcmp( char *s1, char *s2 );</p>
+ as: extern int strcmp(char *s1, char *s2);</p>
- <p>I could then not use it to compare argv's in main: int main( int
- argc, const char *argv[] ) { strcmp( argv[0], "privoxy" ); }</p>
+ <p>I could then not use it to compare argv's in main: int main(int
+ argc, const char *argv[]) { strcmp(argv[0], "privoxy"); }</p>
<p>Both these pointers are *const*! If the c runtime library
maintainers do it, we should too.</p>
<p>Most structures cannot fit onto a normal stack entry (i.e. they
are not 4 bytes or less). Aka, a function declaration like: int
- load_aclfile( struct client_state csp )</p>
+ load_aclfile(struct client_state csp)</p>
<p>would not work. So, to be consistent, we should declare all
- prototypes with "pass by value": int load_aclfile( struct
- client_state *csp )</p>
+ prototypes with "pass by value": int load_aclfile(struct client_state
+ *csp)</p>
</div>
<div class="SECT3">
<tr>
<td>
<pre class="PROGRAMLISTING">
-switch( hash_string( cmd ) )
+switch (hash_string(cmd))
{
- case hash_actions_file :
+ case hash_actions_file:
... code ...
break;
- case hash_confdir :
+ case hash_confdir:
... code ...
break;
- default :
+ default:
log_error( ... );
... anomaly code goes here ...
continue; / break; / exit( 1 ); / etc ...
-} /* end switch( hash_string( cmd ) ) */
+} /* end switch (hash_string(cmd)) */
</pre>
</td>
</tr>
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S39" id="S39">4.7.4. Use 'long' or 'short'
- Instead of 'int'</a></h3>
-
- <p><span class="emphasis"><i class=
- "EMPHASIS">Explanation:</i></span></p>
-
- <p>On 32-bit platforms, int usually has the range of long. On 16-bit
- platforms, int has the range of short.</p>
-
- <p><span class="emphasis"><i class="EMPHASIS">Status:</i></span>
- open-to-debate. In the case of most FSF projects (including
- X/GNU-Emacs), there are typedefs to int4, int8, int16, (or
- equivalence ... I forget the exact typedefs now). Should we add these
- to IJB now that we have a "configure" script?</p>
- </div>
-
- <div class="SECT3">
- <h3 class="SECT3"><a name="S40" id="S40">4.7.5. Don't mix size_t and
+ <h3 class="SECT3"><a name="S40" id="S40">4.7.4. Don't mix size_t and
other types</a></h3>
<p><span class="emphasis"><i class=
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S41" id="S41">4.7.6. Declare each variable
+ <h3 class="SECT3"><a name="S41" id="S41">4.7.5. Declare each variable
and struct on its own line.</a></h3>
<p><span class="emphasis"><i class=
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S42" id="S42">4.7.7. Use malloc/zalloc
+ <h3 class="SECT3"><a name="S42" id="S42">4.7.6. Use malloc/zalloc
sparingly</a></h3>
<p><span class="emphasis"><i class=
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S43" id="S43">4.7.8. The Programmer Who
+ <h3 class="SECT3"><a name="S43" id="S43">4.7.7. The Programmer Who
Uses 'malloc' is Responsible for Ensuring 'free'</a></h3>
<p><span class="emphasis"><i class=
<tr>
<td>
<pre class="PROGRAMLISTING">
-int load_re_filterfile( struct client_state *csp ) { ... }
-static void unload_re_filterfile( void *f ) { ... }
+int load_re_filterfile(struct client_state *csp) { ... }
+static void unload_re_filterfile(void *f) { ... }
</pre>
</td>
</tr>
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S44" id="S44">4.7.9. Add loaders to the
+ <h3 class="SECT3"><a name="S44" id="S44">4.7.8. Add loaders to the
`file_list' structure and in order</a></h3>
<p><span class="emphasis"><i class=
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="S45" id="S45">4.7.10. "Uncertain" new code
- and/or changes to existing code, use FIXME or XXX</a></h3>
+ <h3 class="SECT3"><a name="S45" id="S45">4.7.9. "Uncertain" new code
+ and/or changes to existing code, use XXX</a></h3>
<p><span class="emphasis"><i class=
"EMPHASIS">Explanation:</i></span></p>
<p>If you have enough confidence in new code or confidence in your
changes, but are not *quite* sure of the repercussions, add this:</p>
- <p>/* FIXME: this code has a logic error on platform XYZ, *
- attempting to fix */ #ifdef PLATFORM ...changed code here...
- #endif</p>
+ <p>/* XXX: this code has a logic error on platform XYZ, * attempting
+ to fix */ #ifdef PLATFORM ...changed code here... #endif</p>
<p>or:</p>
- <p>/* FIXME: I think the original author really meant this... */
+ <p>/* XXX: I think the original author really meant this... */
...changed code here...</p>
<p>or:</p>
- <p>/* FIXME: new code that *may* break something else... */ ...new
- code here...</p>
+ <p>/* XXX: new code that *may* break something else... */ ...new code
+ here...</p>
<p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> If you
make it clear that this may or may not be a "good thing (tm)", it
<tr>
<td>
<pre class="PROGRAMLISTING">
-const char FILENAME_rcs[] = "$Id$";
+const char FILENAME_rcs[] = "$I<!-- Break CVS Substitution -->d$";
/*********************************************************************
*
- * File : $Source$
+ * File : $S<!-- Break CVS Substitution -->ource$
*
* Purpose : (Fill me in with a good description!)
*
<pre class="PROGRAMLISTING">
#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id$"
+#define FILENAME_H_VERSION "$I<!-- Break CVS Substitution -->d$"
/*********************************************************************
*
- * File : $Source$
+ * File : $S<!-- Break CVS Substitution -->ource$
*
* Purpose : (Fill me in with a good description!)
*
* Returns : 0 => Ok, everything else is an error.
*
*********************************************************************/
-int FUNCTION_NAME( void *param1, const char *x )
+int FUNCTION_NAME(void *param1, const char *x)
{
...
- return( 0 );
+ return 0;
}
</pre>
"CITETITLE">GNU General Public License</i>.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1231" id="AEN1231">9.1. License</a></h2>
+ <h2 class="SECT2"><a name="AEN1232" id="AEN1232">9.1. License</a></h2>
<p><span class="APPLICATION">Privoxy</span> is free software; you can
redistribute it and/or modify it under the terms of the <i class=
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1247" id="AEN1247">9.2. History</a></h2>
+ <h2 class="SECT2"><a name="AEN1248" id="AEN1248">9.2. History</a></h2>
- <p>A long time ago, there was the <a href=
- "http://www.junkbusters.com/ijb.html" target="_top"><span class=
- "APPLICATION">Internet Junkbuster</span></a>, by Anonymous Coders and
- <a href="http://www.junkbusters.com/" target="_top">Junkbusters
- Corporation</a>. This saved many users a lot of pain in the early days
- of web advertising and user tracking.</p>
+ <p>A long time ago, there was the <span class="APPLICATION">Internet
+ Junkbuster</span>, by Anonymous Coders and Junkbusters Corporation.
+ This saved many users a lot of pain in the early days of web
+ advertising and user tracking.</p>
<p>But the web, its protocols and standards, and with it, the
techniques for forcing ads on users, give up autonomy over their
browsing, and for tracking them, keeps evolving. Unfortunately, the
<span class="APPLICATION">Internet Junkbuster</span> did not. Version
- 2.0.2, published in 1998, was (and is) the last official <a href=
- "http://www.junkbusters.com/ijbdist.html#release" target=
- "_top">release</a> available from <a href="http://www.junkbusters.com"
- target="_top">Junkbusters Corporation</a>. Fortunately, it had been
- released under the GNU <a href=
- "http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target=
- "_top">GPL</a>, which allowed further development by others.</p>
+ 2.0.2, published in 1998, was the last official release, available from
+ Junkbusters Corporation. Fortunately, it had been released under the
+ GNU <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"
+ target="_top">GPL</a>, which allowed further development by others.</p>
<p>So Stefan Waldherr started maintaining an improved version of the
software, to which eventually a number of people contributed patches.
<p>The result of this is <span class="APPLICATION">Privoxy</span>,
whose first stable version, 3.0, was released August, 2002.</p>
+
+ <p>As of 2012 the Junkbusters Corporation's website
+ (http://www.junkbusters.com/) has been shut down, but Privoxy is still
+ actively maintained.</p>
</div>
</div>
"_top">http://ijbswa.cvs.sourceforge.net/ijbswa/</a>, which might help
with visualizing how these pieces fit together.</p>
- <p>Branches are used to fork a sub-development path from the main
- trunk. Within the <tt class="LITERAL">current</tt> module where the
- sources are, there is always at least one <span class=
- "QUOTE">"branch"</span> from the main trunk devoted to a stable release
- series. The main trunk is where active development takes place for the
- next stable series (e.g. 3.2.x). So just prior to each stable series
- (e.g. 3.0.x), a branch is created just for stable series releases (e.g.
- 3.0.0 -> 3.0.1 -> 3.0.2, etc). Once the initial stable release of
- any stable branch has taken place, this branch is <span class=
- "emphasis"><i class="EMPHASIS">only used for bugfixes</i></span>, which
- have had prior testing before being committed to CVS. (See <a href=
- "newrelease.html#VERSIONNUMBERS">Version Numbers</a> below for details
- on versioning.)</p>
-
<p>At one time there were two distinct branches: stable and unstable.
The more drastic changes were to be in the unstable branch. These
branches have now been merged to minimize time and effort of
<p>The source tree is the heart of every software project. Every effort
must be made to ensure that it is readable, compilable and consistent
- at all times. There are differing guidelines for the stable branch and
- the main development trunk, and we ask anyone with CVS access to
- strictly adhere to the following guidelines:</p>
+ at all times. We expect anyone with CVS access to strictly adhere to
+ the following guidelines:</p>
<p>Basic Guidelines, for all branches:</p>
<p>Packagers are encouraged to include this documentation. For those
without the ability to build the docs locally, text versions of each are
kept in CVS. HTML versions are also being kept in CVS under <tt class=
- "FILENAME">doc/webserver/*</tt>. And PDF version are kept in <tt class=
- "FILENAME">doc/pdf/*</tt>.</p>
+ "FILENAME">doc/webserver/*</tt>.</p>
<p>Formal documents are built with the Makefile targets of <samp class=
- "COMPUTEROUTPUT">make dok</samp>, or alternately <samp class=
- "COMPUTEROUTPUT">make redhat-dok</samp>. If you have problems, try both.
- The build process uses the document SGML sources in <samp class=
- "COMPUTEROUTPUT">doc/source/*/*</samp> to update all text files in
- <samp class="COMPUTEROUTPUT">doc/text/</samp> and to update all HTML
- documents in <samp class="COMPUTEROUTPUT">doc/webserver/</samp>.</p>
+ "COMPUTEROUTPUT">make dok</samp>. The build process uses the document
+ SGML sources in <samp class="COMPUTEROUTPUT">doc/source/*/*</samp> to
+ update all text files in <samp class="COMPUTEROUTPUT">doc/text/</samp>
+ and to update all HTML documents in <samp class=
+ "COMPUTEROUTPUT">doc/webserver/</samp>.</p>
<p>Documentation writers should please make sure documents build
successfully before committing to CVS, if possible.</p>
<ol type="1">
<li>
<p>First, build the docs by running <samp class="COMPUTEROUTPUT">make
- dok</samp> (or alternately <samp class="COMPUTEROUTPUT">make
- redhat-dok</samp>). For PDF docs, do <samp class=
- "COMPUTEROUTPUT">make dok-pdf</samp>.</p>
+ dok</samp>.</p>
</li>
<li>
<li>
<p>Our documents are available in differing formats. Right now,
- they are just plain text, HTML, and PDF, but others are always a
+ they are just plain text and/or HTML, but others are always a
future possibility. Be careful with URLs (<ulink>), and avoid
this mistake:</p>
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN217" id="AEN217">3.3. Privoxy Custom
+ <h2 class="SECT2"><a name="AEN208" id="AEN208">3.3. Privoxy Custom
Entities</a></h2>
<p><span class="APPLICATION">Privoxy</span> documentation is using a
<td><span class="emphasis"><i class=
"EMPHASIS">p-version</i></span>: the <span class=
"APPLICATION">Privoxy</span> version string, e.g.
- <span class="QUOTE">"3.0.19"</span>.</td>
+ <span class="QUOTE">"3.0.20"</span>.</td>
</tr>
<tr>
2001-2009 by <a href="http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: developer-manual.sgml,v 2.38 2011/12/26
- 17:05:40 fabiankeil Exp $<br></p>
+ <p class="PUBDATE">$Id: developer-manual.sgml,v 2.51 2012/06/19
+ 12:48:04 fabiankeil Exp $<br></p>
<div>
<div class="ABSTRACT">
entirely correct. As always, patches are welcome.</p>
<p>Please note that this document is constantly evolving. This copy
- represents the state at the release of version 3.0.19. You can find
+ represents the state at the release of version 3.0.20. You can find
the latest version of the this manual at <a href=
"http://www.privoxy.org/developer-manual/" target=
"_top">http://www.privoxy.org/developer-manual/</a>. Please see
<dt>3.2. <a href="documentation.html#DOCSTYLE"><span class=
"APPLICATION">Privoxy</span> Documentation Style</a></dt>
- <dt>3.3. <a href="documentation.html#AEN217">Privoxy Custom
+ <dt>3.3. <a href="documentation.html#AEN208">Privoxy Custom
Entities</a></dt>
</dl>
</dd>
<dt>4.7.3. <a href="coding.html#S38">Try to avoid falling
through cases in a switch statement.</a></dt>
- <dt>4.7.4. <a href="coding.html#S39">Use 'long' or 'short'
- Instead of 'int'</a></dt>
-
- <dt>4.7.5. <a href="coding.html#S40">Don't mix size_t and
+ <dt>4.7.4. <a href="coding.html#S40">Don't mix size_t and
other types</a></dt>
- <dt>4.7.
6. <a href="coding.html#S41">Declare each variable
+ <dt>4.7.
5. <a href="coding.html#S41">Declare each variable
and struct on its own line.</a></dt>
- <dt>4.7.
7. <a href="coding.html#S42">Use malloc/zalloc
+ <dt>4.7.
6. <a href="coding.html#S42">Use malloc/zalloc
sparingly</a></dt>
- <dt>4.7.
8. <a href="coding.html#S43">The Programmer Who Uses
+ <dt>4.7.
7. <a href="coding.html#S43">The Programmer Who Uses
'malloc' is Responsible for Ensuring 'free'</a></dt>
- <dt>4.7.
9. <a href="coding.html#S44">Add loaders to the
+ <dt>4.7.
8. <a href="coding.html#S44">Add loaders to the
`file_list' structure and in order</a></dt>
- <dt>4.7.
10. <a href="coding.html#S45">"Uncertain" new code
- and/or changes to existing code, use FIXME or XXX</a></dt>
+ <dt>4.7.
9. <a href="coding.html#S45">"Uncertain" new code
+ and/or changes to existing code, use XXX</a></dt>
</dl>
</dd>
<dd>
<dl>
- <dt>9.1. <a href="copyright.html#AEN1231">License</a></dt>
+ <dt>9.1. <a href="copyright.html#AEN1232">License</a></dt>
- <dt>9.2. <a href="copyright.html#AEN1247">History</a></dt>
+ <dt>9.2. <a href="copyright.html#AEN1248">History</a></dt>
</dl>
</dd>
<tr>
<td>
<pre class="PROGRAMLISTING">
- debchange -v 3.0.19-stable-1 "New upstream version"
+ debchange -v 3.0.20-UNRELEASED-1 "New upstream version"
</pre>
</td>
</tr>
</table>
<p>This will create <tt class=
- "FILENAME">../privoxy_3.0.19-stable-1_i386.deb</tt> which can be
+ "FILENAME">../privoxy_3.0.20-UNRELEASED-1_i386.deb</tt> which can be
uploaded. To upload the package to Sourceforge, simply issue</p>
<table border="0" bgcolor="#E0E0E0" width="100%">
<p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
you have freshly exported the right version into an empty
- directory</i></span>. (See "Building and releasing packages" above).
- Then get the Mac OS X setup module:</p>
+ directory</i></span>. (See "Building and releasing packages"
+ above).</p>
- <table border="0" bgcolor="#E0E0E0" width="100%">
- <tr>
- <td>
- <pre class="PROGRAMLISTING">
+ <p>There are three modules available in the CVS repository for use on
+ Mac OS X, though technically only two of them generate a release (the
+ other can be used to install from source).</p>
+
+ <div class="SECT4">
+ <h4 class="SECT4"><a name="OS-X-OSXPACKAGEBUILDER-MODULE" id=
+ "OS-X-OSXPACKAGEBUILDER-MODULE">6.3.8.1. OSXPackageBuilder
+ module</a></h4>
+
+ <p>The OSXPackageBuilder module generates OS X installer packages
+ supporting all Macs running OS X 10.4 and above. Obtain it from CVS
+ as follows into a folder parallel to the exported privoxy
+ source:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="PROGRAMLISTING">
+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>The module contains complete instructions on its usage in the
+ file <tt class="FILENAME">OS X Package Builder HOWTO.txt</tt>.</p>
+
+ <p>Once the package(s) have been generated, you can then upload
+ them directly to the Files section of the Sourceforge project in
+ the Macintosh (OS X) folder. Each new version release of Privoxy
+ should have a new subfolder created in which to store its files.
+ Please ensure that the folder contains a readme file that makes it
+ clear which package is for whichversion of OS X.</p>
+ </div>
+
+ <div class="SECT4">
+ <h4 class="SECT4"><a name="OS-X-OSXSETUP-MODULE" id=
+ "OS-X-OSXSETUP-MODULE">6.3.8.2. osxsetup module
+ (DEPRECATED)</a></h4>
+
+ <p><span class="emphasis"><i class="EMPHASIS">This module is
+ deprecated since the installer it generates places all Privoxy
+ files in one folder in a non-standard location, and supports only
+ Intel Macs running OS X 10.6 or higher.</i></span></p>
+
+ <p>Check out the module from CVS as follows into a folder parallel
+ to the exported privoxy source:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="PROGRAMLISTING">
cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup
</pre>
- </td>
- </tr>
- </table>
+ </td>
+ </tr>
+ </table>
- <p>Then run:</p>
- <table border="0" bgcolor="#E0E0E0" width="100%">
- <tr>
- <td>
- <pre class="PROGRAMLISTING">
+
<table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+
<pre class="PROGRAMLISTING">
cd osxsetup
build
</pre>
- </td>
- </tr>
- </table>
+ </td>
+ </tr>
+ </table>
- <p>This will run <tt class="FILENAME">autoheader</tt>, <tt class=
- "FILENAME">autoconf</tt> and <tt class="FILENAME">configure</tt> as
- well as <tt class="FILENAME">make</tt>. Finally, it will copy over
- the necessary files to the ./osxsetup/files directory for further
- processing by <tt class="FILENAME">PackageMaker</tt>.</p>
+
<p>This will run <tt class="FILENAME">autoheader</tt>, <tt class=
+ "FILENAME">autoconf</tt> and <tt class="FILENAME">configure</tt> as
+ well as <tt class="FILENAME">make</tt>. Finally, it will copy over
+ the necessary files to the ./osxsetup/files directory for further
+ processing by <tt class="FILENAME">PackageMaker</tt>.</p>
- <p>Bring up PackageMaker with the PrivoxyPackage.pmsp definition
- file, modify the package name to match the release, and hit the
- "Create package" button. If you specify ./Privoxy.pkg as the output
- package name, you can then create the distributable zip file with the
- command:</p>
+
<p>Bring up PackageMaker with the PrivoxyPackage.pmsp definition
+ file, modify the package name to match the release, and hit the
+ "Create package" button. If you specify ./Privoxy.pkg as the output
+ package name, you can then create the distributable zip file with
+ the command:</p>
- <table border="0" bgcolor="#E0E0E0" width="100%">
- <tr>
- <td>
- <pre class="PROGRAMLISTING">
+
<table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+
<pre class="PROGRAMLISTING">
zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
</pre>
- </td>
- </tr>
- </table>
+ </td>
+ </tr>
+ </table>
+
+ <p>You can then upload this file directly to the Files section of
+ the Sourceforge project in the Macintosh (OS X) folder. Each new
+ version release of Privoxy should have a new subfolder created in
+ which to store its files. Please ensure that the folder contains a
+ readme file that makes it clear which version(s) of OS X the
+ package supports.</p>
+ </div>
+
+ <div class="SECT4">
+ <h4 class="SECT4"><a name="OS-X-MACSETUP-MODULE" id=
+ "OS-X-MACSETUP-MODULE">6.3.8.3. macsetup module</a></h4>
+
+ <p>The macsetup module is ideal if you wish to build and install
+ Privoxy from source on a single machine.</p>
+
+ <p>Check out the module from CVS as follows into a folder parallel
+ to the exported privoxy source:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="PROGRAMLISTING">
+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup
+</pre>
+ </td>
+ </tr>
+ </table>
- <p>You can then upload <tt class=
- "FILENAME">privoxyosx_setup_x.y.z.zip</tt> anonymously to <tt class=
- "FILENAME">uploads.sourceforge.net/incoming</tt>, create a release
- for it, and you're done. Use the release notes and Change Log from
- the source tarball package.</p>
+ <p>The module contains complete instructions on its usage in its
+ <tt class="FILENAME">README</tt> file. The end result will be the
+ exported version of Privoxy installed on the build machine.</p>
+ </div>
</div>
<div class="SECT3">
column, and click <tt class="LITERAL">Add Release</tt>. You will then
need to create a new release for your package, using the format of
<tt class="LITERAL">$VERSION ($CODE_STATUS)</tt>, e.g. <span class=
- "emphasis"><i class="EMPHASIS">3.0.19 (beta)</i></span>.</p>
+ "emphasis"><i class="EMPHASIS">3.0.20 (beta)</i></span>.</p>
<p>Now just follow the prompts. Be sure to add any appropriate Release
notes. You should see your freshly uploaded packages in <span class=
</tbody>
</table>
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ht/en/cookies.html" target=
- "_top">http://www.junkbusters.com/ht/en/cookies.html</a>, an
- explanation how cookies are used to track web users.</td>
- </tr>
- </tbody>
- </table>
-
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ijb.html" target=
- "_top">http://www.junkbusters.com/ijb.html</a>, the original
- Internet Junkbuster.</td>
- </tr>
- </tbody>
- </table>
-
<table border="0">
<tbody>
<tr>
Configuration</a></h1>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN369" id="AEN369">3.1. What exactly is an
+ <h3 class="SECT2"><a name="AEN366" id="AEN366">3.1. What exactly is an
<span class="QUOTE">"actions"</span> file?</a></h3>
<p><span class="APPLICATION">Privoxy</span> utilizes the concept of
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN392" id="AEN392">3.3. How are actions
+ <h3 class="SECT2"><a name="AEN389" id="AEN389">3.3. How are actions
files configured? What is the easiest way to do this?</a></h3>
<p>Actions files are just text files in a special syntax and can be
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN401" id="AEN401">3.4. There are several
+ <h3 class="SECT2"><a name="AEN398" id="AEN398">3.4. There are several
different <span class="QUOTE">"actions"</span> files. What are the
differences?</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN489" id="AEN489">3.11. What is the
+ <h3 class="SECT2"><a name="AEN486" id="AEN486">3.11. What is the
<tt class="FILENAME">default.filter</tt> file? What is a <span class=
"QUOTE">"filter"</span>?</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN540" id="AEN540">3.13. Instead of ads,
+ <h3 class="SECT2"><a name="AEN537" id="AEN537">3.13. Instead of ads,
now I get a checkerboard pattern. I don't want to see
anything.</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN557" id="AEN557">3.14. Why would anybody
+ <h3 class="SECT2"><a name="AEN554" id="AEN554">3.14. Why would anybody
want to see a checkerboard pattern?</a></h3>
<p>Remember that <a href="general.html#WHATSANAD">telling which image
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN563" id="AEN563">3.15. I see some images
+ <h3 class="SECT2"><a name="AEN560" id="AEN560">3.15. I see some images
being replaced with text instead of the checkerboard image. Why and how
do I get rid of this?</a></h3>
"APPLICATION">Privoxy</span>.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1475" id="AEN1475">7.1. License</a></h2>
+ <h2 class="SECT2"><a name="AEN1466" id="AEN1466">7.1. License</a></h2>
<p><span class="APPLICATION">Privoxy</span> is free software; you can
redistribute it and/or modify it under the terms of the <i class=
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1491" id="AEN1491">7.2. History</a></h2>
+ <h2 class="SECT2"><a name="AEN1482" id="AEN1482">7.2. History</a></h2>
- <p>A long time ago, there was the <a href=
- "http://www.junkbusters.com/ijb.html" target="_top"><span class=
- "APPLICATION">Internet Junkbuster</span></a>, by Anonymous Coders and
- <a href="http://www.junkbusters.com/" target="_top">Junkbusters
- Corporation</a>. This saved many users a lot of pain in the early days
- of web advertising and user tracking.</p>
+ <p>A long time ago, there was the <span class="APPLICATION">Internet
+ Junkbuster</span>, by Anonymous Coders and Junkbusters Corporation.
+ This saved many users a lot of pain in the early days of web
+ advertising and user tracking.</p>
<p>But the web, its protocols and standards, and with it, the
techniques for forcing ads on users, give up autonomy over their
browsing, and for tracking them, keeps evolving. Unfortunately, the
<span class="APPLICATION">Internet Junkbuster</span> did not. Version
- 2.0.2, published in 1998, was (and is) the last official <a href=
- "http://www.junkbusters.com/ijbdist.html#release" target=
- "_top">release</a> available from <a href="http://www.junkbusters.com"
- target="_top">Junkbusters Corporation</a>. Fortunately, it had been
- released under the GNU <a href=
- "http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target=
- "_top">GPL</a>, which allowed further development by others.</p>
+ 2.0.2, published in 1998, was the last official release, available from
+ Junkbusters Corporation. Fortunately, it had been released under the
+ GNU <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"
+ target="_top">GPL</a>, which allowed further development by others.</p>
<p>So Stefan Waldherr started maintaining an improved version of the
software, to which eventually a number of people contributed patches.
<p>The result of this is <span class="APPLICATION">Privoxy</span>,
whose first stable version, 3.0, was released August, 2002.</p>
+
+ <p>As of 2012 the Junkbusters Corporation's website
+ (http://www.junkbusters.com/) has been shut down, but Privoxy is still
+ actively maintained.</p>
</div>
</div>
<h3 class="SECT2"><a name="NEWJB" id="NEWJB">1.5. What is this new
version of <span class="QUOTE">"Junkbuster"</span>?</a></h3>
- <p>A long time ago, there was the <a href=
- "http://www.junkbusters.com/ijb.html" target="_top"><span class=
- "APPLICATION">Internet Junkbuster</span></a>, by Anonymous Coders and
- <a href="http://www.junkbusters.com/" target="_top">Junkbusters
- Corporation</a>. This saved many users a lot of pain in the early days
- of web advertising and user tracking.</p>
+ <p>A long time ago, there was the <span class="APPLICATION">Internet
+ Junkbuster</span>, by Anonymous Coders and Junkbusters Corporation.
+ This saved many users a lot of pain in the early days of web
+ advertising and user tracking.</p>
<p>But the web, its protocols and standards, and with it, the
techniques for forcing ads on users, give up autonomy over their
browsing, and for tracking them, keeps evolving. Unfortunately, the
<span class="APPLICATION">Internet Junkbuster</span> did not. Version
- 2.0.2, published in 1998, was (and is) the last official <a href=
- "http://www.junkbusters.com/ijbdist.html#release" target=
- "_top">release</a> available from <a href="http://www.junkbusters.com"
- target="_top">Junkbusters Corporation</a>. Fortunately, it had been
- released under the GNU <a href=
- "http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target=
- "_top">GPL</a>, which allowed further development by others.</p>
+ 2.0.2, published in 1998, was the last official release, available from
+ Junkbusters Corporation. Fortunately, it had been released under the
+ GNU <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"
+ target="_top">GPL</a>, which allowed further development by others.</p>
<p>So Stefan Waldherr started maintaining an improved version of the
software, to which eventually a number of people contributed patches.
<p>The result of this is <span class="APPLICATION">Privoxy</span>,
whose first stable version, 3.0, was released August, 2002.</p>
+
+ <p>As of 2012 the Junkbusters Corporation's website
+ (http://www.junkbusters.com/) has been shut down, but Privoxy is still
+ actively maintained.</p>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN85" id="AEN85">1.6. Why <span class=
+ <h3 class="SECT2"><a name="AEN82" id="AEN82">1.6. Why <span class=
"QUOTE">"Privoxy"</span>? Why change the name from Junkbuster at
all?</a></h3>
- <p>Though outdated, <a href="http://junkbusters.com/" target=
- "_top">Junkbusters Corporation</a> continues to offer their original
- version of the <span class="APPLICATION">Internet Junkbuster</span>, so
- publishing our <span class="APPLICATION">Junkbuster</span>-derived
- software under the same name led to confusion.</p>
+ <p>Though outdated, Junkbusters Corporation continued to offer their
+ original version of the <span class="APPLICATION">Internet
+ Junkbuster</span> for a while, so publishing our <span class=
+ "APPLICATION">Junkbuster</span>-derived software under the same name
+ would have led to confusion.</p>
- <p>There are also potential legal complications from our use of the
- <span class="APPLICATION">Junkbuster</span> name, which is a registered
- trademark of <a href="http://junkbusters.com/" target=
- "_top">Junkbusters Corporation</a>. There are, however, no objections
- from Junkbusters Corporation to the <span class=
- "APPLICATION">Privoxy</span> project itself, and they, in fact, still
- share our ideals and goals.</p>
+ <p>There were also potential legal reasons not to use the <span class=
+ "APPLICATION">Junkbuster</span> name, as it was (and maybe still is) a
+ registered trademark of Junkbusters Corporation. There were, however,
+ no objections from Junkbusters Corporation to the <span class=
+ "APPLICATION">Privoxy</span> project itself, and they, in fact, shared
+ our ideals and goals.</p>
- <p>The developers also believed that there are so many improvements
- over the original code, that it was time to make a clean break from the
- past and make a name in their own right.</p>
+ <p>The Privoxy developers also believed that there were so many
+ improvements over the original code, that it was time to make a clean
+ break from the past and make a name in their own right.</p>
<p><span class="APPLICATION">Privoxy</span> is the <span class=
"QUOTE">"<span class="emphasis"><i class="EMPHASIS">Privacy Enhancing
differ from the old Junkbuster?</a></h3>
<p><span class="APPLICATION">Privoxy</span> picks up where <span class=
- "APPLICATION">Junkbuster</span> left off. The new <span class=
+ "APPLICATION">Junkbuster</span> left off. <span class=
"APPLICATION">Privoxy</span> still blocks ads and banners, still
manages <a href="http://en.wikipedia.org/wiki/Browser_cookie" target=
"_top">cookies</a>, and still helps protect your privacy. But, most of
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN163" id="AEN163">1.9. Can Privoxy make
+ <h3 class="SECT2"><a name="AEN158" id="AEN158">1.9. Can Privoxy make
mistakes? This does not sound very scientific.</a></h3>
<p>Actually, it's a black art ;-) And yes, it is always possible to
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN169" id="AEN169">1.10. Will I have to
+ <h3 class="SECT2"><a name="AEN164" id="AEN164">1.10. Will I have to
configure Privoxy before I can use it?</a></h3>
<p>That depends on your expectations. The default installation should
2001-2011 by <a href="http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: faq.sgml,v 2.85 2011/12/26 17:05:40 fabiankeil
+ <p class="PUBDATE">$Id: faq.sgml,v 2.89 2012/06/19 12:49:48 fabiankeil
Exp $<br></p>
<div>
</ul>
<p>Please note that this document is a work in progress. This copy
- represents the state at the release of version 3.0.19. You can find
+ represents the state at the release of version 3.0.20. You can find
the latest version of the document at <a href=
"http://www.privoxy.org/faq/" target=
"_top">http://www.privoxy.org/faq/</a>. Please see the <a href=
<dt>1.5. <a href="general.html#NEWJB">What is this new version of
<span class="QUOTE">"Junkbuster"</span>?</a></dt>
- <dt>1.6. <a href="general.html#AEN85">Why <span class=
+ <dt>1.6. <a href="general.html#AEN82">Why <span class=
"QUOTE">"Privoxy"</span>? Why change the name from Junkbuster at
all?</a></dt>
<dt>1.8. <a href="general.html#WHATSANAD">How does Privoxy know
what is an ad, and what is not?</a></dt>
- <dt>1.9. <a href="general.html#AEN163">Can Privoxy make mistakes?
+ <dt>1.9. <a href="general.html#AEN158">Can Privoxy make mistakes?
This does not sound very scientific.</a></dt>
- <dt>1.10. <a href="general.html#AEN169">Will I have to configure
+ <dt>1.10. <a href="general.html#AEN164">Will I have to configure
Privoxy before I can use it?</a></dt>
<dt>1.11. <a href="general.html#LAN">Can Privoxy run as a server
<dd>
<dl>
- <dt>3.1. <a href="configuration.html#AEN369">What exactly is an
+ <dt>3.1. <a href="configuration.html#AEN366">What exactly is an
<span class="QUOTE">"actions"</span> file?</a></dt>
<dt>3.2. <a href="configuration.html#ACTIONSS">The <span class=
"QUOTE">"actions"</span> concept confuses me. Please list some of
these <span class="QUOTE">"actions"</span>.</a></dt>
- <dt>3.3. <a href="configuration.html#AEN392">How are actions
+ <dt>3.3. <a href="configuration.html#AEN389">How are actions
files configured? What is the easiest way to do this?</a></dt>
- <dt>3.4. <a href="configuration.html#AEN401">There are several
+ <dt>3.4. <a href="configuration.html#AEN398">There are several
different <span class="QUOTE">"actions"</span> files. What are
the differences?</a></dt>
change the configuration with a browser? Does that not raise
security issues?</a></dt>
- <dt>3.11. <a href="configuration.html#AEN489">What is the
+ <dt>3.11. <a href="configuration.html#AEN486">What is the
<tt class="FILENAME">default.filter</tt> file? What is a
<span class="QUOTE">"filter"</span>?</a></dt>
<dt>3.12. <a href="configuration.html#LANCONFIG">How can I set up
Privoxy to act as a proxy for my LAN?</a></dt>
- <dt>3.13. <a href="configuration.html#AEN540">Instead of ads, now
+ <dt>3.13. <a href="configuration.html#AEN537">Instead of ads, now
I get a checkerboard pattern. I don't want to see
anything.</a></dt>
- <dt>3.14. <a href="configuration.html#AEN557">Why would anybody
+ <dt>3.14. <a href="configuration.html#AEN554">Why would anybody
want to see a checkerboard pattern?</a></dt>
- <dt>3.15. <a href="configuration.html#AEN563">I see some images
+ <dt>3.15. <a href="configuration.html#AEN560">I see some images
being replaced with text instead of the checkerboard image. Why
and how do I get rid of this?</a></dt>
<dd>
<dl>
- <dt>4.1. <a href="misc.html#AEN738">How much does Privoxy slow my
+ <dt>4.1. <a href="misc.html#AEN735">How much does Privoxy slow my
browsing down? This has to add extra time to browsing.</a></dt>
<dt>4.2. <a href="misc.html#LOADINGTIMES">I notice considerable
<dt>4.7. <a href="misc.html#IP">How can I hide my IP
address?</a></dt>
- <dt>4.8. <a href="misc.html#AEN803">Can Privoxy guarantee I am
+ <dt>4.8. <a href="misc.html#AEN800">Can Privoxy guarantee I am
anonymous?</a></dt>
- <dt>4.9. <a href="misc.html#AEN821">A test site says I am not
+ <dt>4.9. <a href="misc.html#AEN818">A test site says I am not
using a Proxy.</a></dt>
<dt>4.10. <a href="misc.html#TOR">How do I use Privoxy together
with Tor?</a></dt>
- <dt>4.11. <a href="misc.html#AEN877">Might some things break
+ <dt>4.11. <a href="misc.html#AEN874">Might some things break
because header information or content is being altered?</a></dt>
- <dt>4.12. <a href="misc.html#AEN891">Can Privoxy act as a
+ <dt>4.12. <a href="misc.html#AEN888">Can Privoxy act as a
<span class="QUOTE">"caching"</span> proxy to speed up web
browsing?</a></dt>
- <dt>4.13. <a href="misc.html#AEN901">What about as a firewall?
+ <dt>4.13. <a href="misc.html#AEN898">What about as a firewall?
Can Privoxy protect me?</a></dt>
- <dt>4.14. <a href="misc.html#AEN906">I have large empty spaces /
+ <dt>4.14. <a href="misc.html#AEN903">I have large empty spaces /
a checkerboard pattern now where ads used to be. Why?</a></dt>
- <dt>4.15. <a href="misc.html#AEN914">How can Privoxy filter
+ <dt>4.15. <a href="misc.html#AEN911">How can Privoxy filter
Secure (HTTPS) URLs?</a></dt>
- <dt>4.16. <a href="misc.html#AEN928">Privoxy runs as a
+ <dt>4.16. <a href="misc.html#AEN925">Privoxy runs as a
<span class="QUOTE">"server"</span>. How secure is it? Do I need
to take any special precautions?</a></dt>
<dd>
<dl>
- <dt>5.1. <a href="trouble.html#AEN1100">I cannot connect to any
+ <dt>5.1. <a href="trouble.html#AEN1091">I cannot connect to any
websites. Or, I am getting <span class="QUOTE">"connection
refused"</span> message with every web page. Why?</a></dt>
<dt>5.2. <a href="trouble.html#ERROR503">Why am I getting a 503
Error (WSAECONNREFUSED) on every page?</a></dt>
- <dt>5.3. <a href="trouble.html#AEN1123">I just added a new rule,
+ <dt>5.3. <a href="trouble.html#AEN1114">I just added a new rule,
but the steenkin ad is still getting through. How?</a></dt>
<dt>5.4. <a href="trouble.html#BADSITE">One of my favorite sites
<dd>
<dl>
- <dt>7.1. <a href="copyright.html#AEN1475">License</a></dt>
+ <dt>7.1. <a href="copyright.html#AEN1466">License</a></dt>
- <dt>7.2. <a href="copyright.html#AEN1491">History</a></dt>
+ <dt>7.2. <a href="copyright.html#AEN1482">History</a></dt>
</dl>
</dd>
</dl>
systems are supported?</a></h3>
<p>At present, <span class="APPLICATION">Privoxy</span> is known to run
- on Windows(95, 98, ME, 2000, XP, Vista), GNU/Linux (RedHat, SuSE,
- Debian, Fedora, Gentoo, Slackware and others), Mac OSX, OS/2, AmigaOS,
- FreeBSD, NetBSD, OpenBSD, Solaris, and various other flavors of
- Unix.</p>
+ on Windows 95 and later versions (98, ME, 2000, XP, Vista, Windows 7
+ etc.), GNU/Linux (RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and
+ others), Mac OS X, OS/2, Haiku, DragonFly, FreeBSD, NetBSD, OpenBSD,
+ Solaris, and various other flavors of Unix.</p>
+
+ <p><span class="APPLICATION">Privoxy</span> used to work on AmigaOS and
+ QNX, too, but the code currently isn't maintained and its status
+ unknown. It might no longer compile, but getting it working again
+ shouldn't be too hard.</p>
<p>But any operating system that runs TCP/IP, can conceivably take
advantage of <span class="APPLICATION">Privoxy</span> in a networked
<h1 class="SECT1"><a name="MISC" id="MISC">4. Miscellaneous</a></h1>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN738" id="AEN738">4.1. How much does
+ <h3 class="SECT2"><a name="AEN735" id="AEN735">4.1. How much does
Privoxy slow my browsing down? This has to add extra time to
browsing.</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN803" id="AEN803">4.8. Can Privoxy
+ <h3 class="SECT2"><a name="AEN800" id="AEN800">4.8. Can Privoxy
guarantee I am anonymous?</a></h3>
<p>No. Your chances of remaining anonymous are improved, but unless you
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN821" id="AEN821">4.9. A test site says I
+ <h3 class="SECT2"><a name="AEN818" id="AEN818">4.9. A test site says I
am not using a Proxy.</a></h3>
<p>Good! Actually, they are probably testing for some other kinds of
<p>Save the modified configuration file and open <a href=
"http://config.privoxy.org/show-status" target=
- "_top">http://config.privoxy.org/show-status/</a> in your browser,
+ "_top">http://config.privoxy.org/show-status</a> in your browser,
confirm that <span class="APPLICATION">Privoxy</span> has reloaded its
configuration and that there are no other forward lines, unless you
know that you need them. If everything looks good, refer to <a href=
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN877" id="AEN877">4.11. Might some things
+ <h3 class="SECT2"><a name="AEN874" id="AEN874">4.11. Might some things
break because header information or content is being altered?</a></h3>
<p>Definitely. It is common for sites to use browser type, browser
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN891" id="AEN891">4.12. Can Privoxy act as
+ <h3 class="SECT2"><a name="AEN888" id="AEN888">4.12. Can Privoxy act as
a <span class="QUOTE">"caching"</span> proxy to speed up web
browsing?</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN901" id="AEN901">4.13. What about as a
+ <h3 class="SECT2"><a name="AEN898" id="AEN898">4.13. What about as a
firewall? Can Privoxy protect me?</a></h3>
<p>Not in the way you mean, or in the way some firewall vendors claim
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN906" id="AEN906">4.14. I have large empty
+ <h3 class="SECT2"><a name="AEN903" id="AEN903">4.14. I have large empty
spaces / a checkerboard pattern now where ads used to be. Why?</a></h3>
<p>It is technically possible to eliminate banners and ads in a way
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN914" id="AEN914">4.15. How can Privoxy
+ <h3 class="SECT2"><a name="AEN911" id="AEN911">4.15. How can Privoxy
filter Secure (HTTPS) URLs?</a></h3>
<p>Since secure HTTP connections are encrypted SSL sessions between
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN928" id="AEN928">4.16. Privoxy runs as a
+ <h3 class="SECT2"><a name="AEN925" id="AEN925">4.16. Privoxy runs as a
<span class="QUOTE">"server"</span>. How secure is it? Do I need to
take any special precautions?</a></h3>
</tbody>
</table>
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ht/en/cookies.html"
- target="_top">http://www.junkbusters.com/ht/en/cookies.html</a>,
- an explanation how cookies are used to track web users.</td>
- </tr>
- </tbody>
- </table>
-
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ijb.html" target=
- "_top">http://www.junkbusters.com/ijb.html</a>, the original
- Internet Junkbuster.</td>
- </tr>
- </tbody>
- </table>
-
<table border="0">
<tbody>
<tr>
Troubleshooting</a></h1>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN1100" id="AEN1100">5.1. I cannot connect
+ <h3 class="SECT2"><a name="AEN1091" id="AEN1091">5.1. I cannot connect
to any websites. Or, I am getting <span class="QUOTE">"connection
refused"</span> message with every web page. Why?</a></h3>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN1123" id="AEN1123">5.3. I just added a
+ <h3 class="SECT2"><a name="AEN1114" id="AEN1114">5.3. I just added a
new rule, but the steenkin ad is still getting through. How?</a></h3>
<p>If the ad had been displayed before you added its URL, it will
<title>Privoxy - Home Page</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <meta name="KEYWORD" content="privoxy">
- <meta name="KEYWORD" content="HTTP">
- <meta name="KEYWORD" content="proxy">
- <meta name="KEYWORD" content="privacy">
- <meta name="KEYWORD" content="popups">
- <meta name="KEYWORD" content="po-ups">
- <meta name="KEYWORD" content="HTML">
- <meta name="KEYWORD" content="JavaScript">
- <meta name="KEYWORD" content="cleaning">
- <meta name="KEYWORD" content="blocking">
- <meta name="KEYWORD" content="cleaner">
- <meta name="KEYWORD" content="blocker">
- <meta name="KEYWORD" content="filter">
- <meta name="KEYWORD" content="proxy">
- <meta name="KEYWORD" content="junk">
- <meta name="KEYWORD" content="ad">
- <meta name="KEYWORD" content="advertisement">
- <meta name="KEYWORD" content="banner">
- <meta name="KEYWORD" content="webbugs">
- <meta name="KEYWORD" content="web-bugs">
- <meta name="KEYWORD" content="werbung">
- <meta name="KEYWORD" content="junkbusters">
- <meta name="KEYWORD" content="junkbuster">
<link rel="STYLESHEET" type="text/css" href="p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="description" content=
"Privoxy helps users to protect their privacy.">
- <meta name="MSSmartTagsPreventParsing" content="TRUE">
</head>
<body class="ARTICLE" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
<div>
<div class="ABSTRACT">
- <a name="AEN28" id="AEN28"></a>
+ <a name="AEN4" id="AEN4"></a>
<p>Privoxy is a non-caching web proxy with advanced filtering
capabilities for enhancing privacy, modifying web page data and
</ul>
<p>The most recent release is <a href="announce.txt" target=
- "_top">3.0.19 (stable)</a>.</p>
+ "_top">3.0.20 (UNRELEASED)</a>.</p>
</div>
</div>
<hr>
<div class="SECT1">
<hr>
- <h2 class="SECT1"><a name="AEN90" id="AEN90"></a></h2>
+ <h2 class="SECT1"><a name="AEN66" id="AEN66"></a></h2>
<div class="INFORMALTABLE">
- <a name="AEN93" id="AEN93"></a>
+ <a name="AEN69" id="AEN69"></a>
<table border="0" frame="void" rules="all" width="100%" class=
"CALSTABLE">
<title>Privoxy - The Privacy Enhancing Proxy</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <meta name="KEYWORD" content="privoxy">
- <meta name="KEYWORD" content="HTTP">
- <meta name="KEYWORD" content="proxy">
- <meta name="KEYWORD" content="privacy">
- <meta name="KEYWORD" content="popups">
- <meta name="KEYWORD" content="po-ups">
- <meta name="KEYWORD" content="HTML">
- <meta name="KEYWORD" content="JavaScript">
- <meta name="KEYWORD" content="cleaning">
- <meta name="KEYWORD" content="blocking">
- <meta name="KEYWORD" content="cleaner">
- <meta name="KEYWORD" content="blocker">
- <meta name="KEYWORD" content="filter">
- <meta name="KEYWORD" content="proxy">
- <meta name="KEYWORD" content="junk">
- <meta name="KEYWORD" content="ad">
- <meta name="KEYWORD" content="advertisement">
- <meta name="KEYWORD" content="banner">
- <meta name="KEYWORD" content="webbugs">
- <meta name="KEYWORD" content="web-bugs">
- <meta name="KEYWORD" content="werbung">
- <meta name="KEYWORD" content="junkbusters">
- <meta name="KEYWORD" content="junkbuster">
<link rel="STYLESHEET" type="text/css" href="p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="description" content=
"Privoxy helps users to protect their privacy.">
- <meta name="MSSmartTagsPreventParsing" content="TRUE">
</head>
<body class="ARTICLE" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
<h1 class="TITLE"><a name="AEN2" id="AEN2">Privoxy - The Privacy
Enhancing Proxy</a></h1>
- <h2 class="SUBTITLE">Project Index Page v3.0.19</h2>
+ <h2 class="SUBTITLE">Project Index Page v3.0.20</h2>
<div>
<div class="ABSTRACT">
- <a name="AEN29" id="AEN29"></a>
+ <a name="AEN5" id="AEN5"></a>
<p>Privoxy is a non-caching web proxy with advanced filtering
capabilities for enhancing privacy, modifying web page data and
<div class="SECT1">
<hr>
- <h2 class="SECT1"><a name="AEN89" id="AEN89"></a></h2>
+ <h2 class="SECT1"><a name="AEN65" id="AEN65"></a></h2>
<p><sub>Copyright © 2001-2010 by Privoxy Developers</sub></p>
</div>
<title>Actions Files</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="The Main Configuration File" href=
"config.html">
<link rel="NEXT" title="Filter Files" href="filter-file.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
in <tt class="FILENAME">default.action</tt> are:</p>
<div class="TABLE">
- <a name="AEN2780" id="AEN2780"></a>
+ <a name="AEN2855" id="AEN2855"></a>
<p><b>Table 1. Default Configurations</b></p>
actions</a>.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN2879" id="AEN2879">8.1. Finding the Right
+ <h2 class="SECT2"><a name="AEN2954" id="AEN2954">8.1. Finding the Right
Mix</a></h2>
<p>Note that some <a href="actions-file.html#ACTIONS">actions</a>, like
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN2886" id="AEN2886">8.2. How to
+ <h2 class="SECT2"><a name="AEN2961" id="AEN2961">8.2. How to
Edit</a></h2>
<p>The easiest way to edit the actions files is with a browser by using
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN2998" id="AEN2998">8.4.1. The Domain
+ <h3 class="SECT3"><a name="AEN3073" id="AEN3073">8.4.1. The Domain
Pattern</a></h3>
<p>The matching of the domain part offers some flexible options: if
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN3074" id="AEN3074">8.4.2. The Path
+ <h3 class="SECT3"><a name="AEN3149" id="AEN3149">8.4.2. The Path
Pattern</a></h3>
<p><span class="APPLICATION">Privoxy</span> uses <span class=
TAG:^User-Agent: Ubuntu APT-HTTP/
TAG:^User-Agent: MPlayer/
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <table border="0" bgcolor="#E0E0E0" width="90%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+# Tag all requests with the Range header set
+{+client-header-tagger{range-requests}}
+/
+
+# Disable filtering for the tagged requests.
+#
+# With filtering enabled Privoxy would remove the Range headers
+# to be able to filter the whole response. The downside is that
+# it prevents clients from resuming downloads or skipping over
+# parts of multimedia files.
+{-filter -deanimate-gifs}
+TAG:^RANGE-REQUEST$
+
</pre>
</td>
</tr>
provided as parameter, or derived by applying a single pcrs
command to the original URL.</p>
+ <p>The syntax for pcrs commands is documented in the <a href=
+ "filter-file.html">filter file</a> section.</p>
+
<p>This action will be ignored if you use it together with
<tt class="LITERAL"><a href=
"actions-file.html#BLOCK">block</a></tt>. It can be combined
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4706" id="AEN4706">8.5.34.
+ <h3 class="SECT3"><a name="AEN4785" id="AEN4785">8.5.34.
Summary</a></h3>
<p>Note that many of these actions have the potential to cause a page
together:</p>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4770" id="AEN4770">8.7.1.
+ <h3 class="SECT3"><a name="AEN4849" id="AEN4849">8.7.1.
match-all.action</a></h3>
<p>Remember <span class="emphasis"><i class="EMPHASIS">all actions
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4792" id="AEN4792">8.7.2.
+ <h3 class="SECT3"><a name="AEN4871" id="AEN4871">8.7.2.
default.action</a></h3>
<p>If you aren't a developer, there's no need for you to edit the
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4905" id="AEN4905">8.7.3.
+ <h3 class="SECT3"><a name="AEN4984" id="AEN4984">8.7.3.
user.action</a></h3>
<p>So far we are painting with a broad brush by setting general
<title>Appendix</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="See Also" href="seealso.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN5795" id="AEN5795">14.2. Privoxy's
+ <h2 class="SECT2"><a name="AEN5865" id="AEN5865">14.2. Privoxy's
Internal Pages</a></h2>
<p>Since <span class="APPLICATION">Privoxy</span> proxies each
<ul>
<li>
- <p>Privoxy main page:</p><a name="AEN5809" id="AEN5809"></a>
+ <p>Privoxy main page:</p><a name="AEN5879" id="AEN5879"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/" target=
<li>
<p>Show information about the current configuration, including
- viewing and editing of actions files:</p><a name="AEN5817" id=
- "AEN5817"></a>
+ viewing and editing of actions files:</p><a name="AEN5887" id=
+ "AEN5887"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-status" target=
</li>
<li>
- <p>Show the source code version numbers:</p><a name="AEN5822" id=
- "AEN5822"></a>
+ <p>Show the source code version numbers:</p><a name="AEN5892" id=
+ "AEN5892"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-version" target=
</li>
<li>
- <p>Show the browser's request headers:</p><a name="AEN5827" id=
- "AEN5827"></a>
+ <p>Show the browser's request headers:</p><a name="AEN5897" id=
+ "AEN5897"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-request" target=
</li>
<li>
- <p>Show which actions apply to a URL and why:</p><a name="AEN5832"
- id="AEN5832"></a>
+ <p>Show which actions apply to a URL and why:</p><a name="AEN5902"
+ id="AEN5902"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-url-info" target=
<span class="QUOTE">"off"</span>, <span class=
"QUOTE">"Privoxy"</span> continues to run, but only as a
pass-through proxy, with no actions taking place:</p><a name=
- "AEN5840" id="AEN5840"></a>
+ "AEN5910" id="AEN5910"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle" target=
"_top">http://config.privoxy.org/toggle</a></p>
</blockquote>
- <p>Short cuts. Turn off, then on:</p><a name="AEN5844" id=
- "AEN5844"></a>
+ <p>Short cuts. Turn off, then on:</p><a name="AEN5914" id=
+ "AEN5914"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle?set=disable" target=
"_top">http://config.privoxy.org/toggle?set=disable</a></p>
- </blockquote><a name="AEN5847" id="AEN5847"></a>
+ </blockquote><a name="AEN5917" id="AEN5917"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle?set=enable" target=
<title>The Main Configuration File</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Privoxy Configuration" href=
"configuration.html">
<link rel="NEXT" title="Actions Files" href="actions-file.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
<p>Your logfile will grow indefinitely, and you will probably
want to periodically remove it. On Unix systems, you can do
this with a cron job (see <span class="QUOTE">"man
- cron"</span>). For Red Hat based Linux distributions, a
- <b class="COMMAND">logrotate</b> script has been included.</p>
+ cron"</span>).</p>
<p>Any log files must be writable by whatever user <span class=
"APPLICATION">Privoxy</span> is being run as (on Unix, default
debug 4096 # Startup banner and warnings.
debug 8192 # Non-fatal errors
debug 32768 # log all data read from the network
+ debug 65536 # Log the applying actions
</pre>
</td>
</tr>
Internet and/or the local network. Be aware that some GNU/Linux
distributions modify that behaviour without updating the
documentation. Check for non-standard patches if your
- <span class="APPLICATION">Privoxy</span>version behaves
+ <span class="APPLICATION">Privoxy</span> version behaves
differently.</p>
- <p>If you configure <span class="APPLICATION">Privoxy</span>to
+ <p>If you configure <span class="APPLICATION">Privoxy</span> to
be reachable from the network, consider using <a href=
"config.html#ACLS">access control lists</a> (ACL's, see below),
and/or a firewall.</p>
"config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a></tt>
and <tt class="LITERAL"><a href=
"config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a></tt></p>
-
- <p>With the exception noted above, listening on multiple
- addresses is currently not supported by <span class=
- "APPLICATION">Privoxy</span> directly. It can be done on most
- operating systems by letting a packet filter redirect request
- for certain addresses to Privoxy, though.</p>
</dd>
<dt>Example:</dt>
<p>Several users have reported this as a Privoxy bug, so the
default value has been reduced. Consider increasing it to 300
seconds or even more if you think your browser can handle it.
- If your browser appears to be hanging it can't.</p>
+ If your browser appears to be hanging, it probably can't.</p>
</dd>
<dt>Examples:</dt>
</div>
</div>
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="TOLERATE-PIPELINING" id=
+ "TOLERATE-PIPELINING">7.6.5. tolerate-pipelining</a></h4>
+
+ <div class="VARIABLELIST">
+ <dl>
+ <dt>Specifies:</dt>
+
+ <dd>
+ <p>Whether or not pipelined requests should be served.</p>
+ </dd>
+
+ <dt>Type of value:</dt>
+
+ <dd>
+ <p><tt class="REPLACEABLE"><i>0 or 1.</i></tt></p>
+ </dd>
+
+ <dt>Default value:</dt>
+
+ <dd>
+ <p>None</p>
+ </dd>
+
+ <dt>Effect if unset:</dt>
+
+ <dd>
+ <p>If Privoxy receives more than one request at once, it
+ terminates the client connection after serving the first
+ one.</p>
+ </dd>
+
+ <dt>Notes:</dt>
+
+ <dd>
+ <p><span class="APPLICATION">Privoxy</span> currently doesn't
+ pipeline outgoing requests, thus allowing pipelining on the
+ client connection is not guaranteed to improve the
+ performance.</p>
+
+ <p>By default <span class="APPLICATION">Privoxy</span> tries to
+ discourage clients from pipelining by discarding aggressively
+ pipelined requests, which forces the client to resend them
+ through a new connection.</p>
+
+ <p>This option lets <span class="APPLICATION">Privoxy</span>
+ tolerate pipelining. Whether or not that improves performance
+ mainly depends on the client configuration.</p>
+
+ <p>This options is new and should be considered
+ experimental.</p>
+ </dd>
+
+ <dt>Examples:</dt>
+
+ <dd>
+ <p>tolerate-pipelining 1</p>
+ </dd>
+ </dl>
+ </div>
+ </div>
+
<div class="SECT3">
<h4 class="SECT3"><a name="DEFAULT-SERVER-TIMEOUT" id=
- "DEFAULT-SERVER-TIMEOUT">7.6.5. default-server-timeout</a></h4>
+ "DEFAULT-SERVER-TIMEOUT">7.6.6. default-server-timeout</a></h4>
<div class="VARIABLELIST">
<dl>
<div class="SECT3">
<h4 class="SECT3"><a name="CONNECTION-SHARING" id=
- "CONNECTION-SHARING">7.6.6. connection-sharing</a></h4>
+ "CONNECTION-SHARING">7.6.7. connection-sharing</a></h4>
<div class="VARIABLELIST">
<dl>
</div>
<div class="SECT3">
- <h4 class="SECT3"><a name="SOCKET-TIMEOUT" id="SOCKET-TIMEOUT">7.6.7.
+ <h4 class="SECT3"><a name="SOCKET-TIMEOUT" id="SOCKET-TIMEOUT">7.6.8.
socket-timeout</a></h4>
<div class="VARIABLELIST">
<div class="SECT3">
<h4 class="SECT3"><a name="MAX-CLIENT-CONNECTIONS" id=
- "MAX-CLIENT-CONNECTIONS">7.6.8. max-client-connections</a></h4>
+ "MAX-CLIENT-CONNECTIONS">7.6.9. max-client-connections</a></h4>
<div class="VARIABLELIST">
<dl>
<div class="SECT3">
<h4 class="SECT3"><a name="HANDLE-AS-EMPTY-DOC-RETURNS-OK" id=
- "HANDLE-AS-EMPTY-DOC-RETURNS-OK">7.6.9.
+ "HANDLE-AS-EMPTY-DOC-RETURNS-OK">7.6.10.
handle-as-empty-doc-returns-ok</a></h4>
<div class="VARIABLELIST">
<div class="SECT3">
<h4 class="SECT3"><a name="ENABLE-COMPRESSION" id=
- "ENABLE-COMPRESSION">7.6.10. enable-compression</a></h4>
+ "ENABLE-COMPRESSION">7.6.11. enable-compression</a></h4>
<div class="VARIABLELIST">
<dl>
<div class="SECT3">
<h4 class="SECT3"><a name="COMPRESSION-LEVEL" id=
- "COMPRESSION-LEVEL">7.6.11. compression-level</a></h4>
+ "COMPRESSION-LEVEL">7.6.12. compression-level</a></h4>
<div class="VARIABLELIST">
<dl>
</dl>
</div>
</div>
+
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="CLIENT-HEADER-ORDER" id=
+ "CLIENT-HEADER-ORDER">7.6.13. client-header-order</a></h4>
+
+ <div class="VARIABLELIST">
+ <dl>
+ <dt>Specifies:</dt>
+
+ <dd>
+ <p>The order in which client headers are sorted before
+ forwarding them.</p>
+ </dd>
+
+ <dt>Type of value:</dt>
+
+ <dd>
+ <p><tt class="REPLACEABLE"><i>Client header names delimited by
+ spaces or tabs</i></tt></p>
+ </dd>
+
+ <dt>Default value:</dt>
+
+ <dd>
+ <p>None</p>
+ </dd>
+
+ <dt>Notes:</dt>
+
+ <dd>
+ <p>By default <span class="APPLICATION">Privoxy</span> leaves
+ the client headers in the order they were sent by the client.
+ Headers are modified in-place, new headers are added at the end
+ of the already existing headers.</p>
+
+ <p>The header order can be used to fingerprint client requests
+ independently of other headers like the User-Agent.</p>
+
+ <p>This directive allows to sort the headers differently to
+ better mimic a different User-Agent. Client headers will be
+ emitted in the order given, headers whose name isn't explicitly
+ specified are added at the end.</p>
+
+ <p>Note that sorting headers in an uncommon way will make
+ fingerprinting actually easier. Encrypted headers are not
+ affected by this directive.</p>
+ </dd>
+ </dl>
+ </div>
+ </div>
</div>
<div class="SECT2">
"LOG-MESSAGES"></a>
<p>If <span class="QUOTE">"log-messages"</span> is set to 1,
- <span class="APPLICATION">Privoxy</span> will log messages to the
- console window:</p>
+ <span class="APPLICATION">Privoxy</span> copy log messages to the
+ console window. The log detail depends on the <a href=
+ "config.html#DEBUG">debug</a> directive.</p>
<p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
"emphasis"><i class="EMPHASIS">log-messages 1</i></span><br>
<title>Privoxy Configuration</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Starting Privoxy" href="startup.html">
<link rel="NEXT" title="The Main Configuration File" href="config.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
controlled easily with a web browser.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1090" id="AEN1090">6.1. Controlling
+ <h2 class="SECT2"><a name="AEN1107" id="AEN1107">6.1. Controlling
Privoxy with Your Web Browser</a></h2>
<p><span class="APPLICATION">Privoxy</span>'s user interface can be
</pre>
- <h2 class="BRIDGEHEAD"><a name="AEN1098" id=
- "AEN1098"></a> Privoxy Menu</h2>
+ <h2 class="BRIDGEHEAD"><a name="AEN1115" id=
+ "AEN1115"></a> Privoxy Menu</h2>
<pre>
</pre>
<tr>
<td>
- ▪ <a href="http://www.privoxy.org/3.0.19/user-manual/"
+ ▪ <a href="http://www.privoxy.org/3.0.20/user-manual/"
target="_top">Documentation</a></td>
</tr>
</tbody>
<p>For Unix, *BSD and Linux, all configuration files are located in
<tt class="FILENAME">/etc/privoxy/</tt> by default. For MS Windows,
OS/2, and AmigaOS these are all in the same directory as the
- <span class="APPLICATION">Privoxy</span> executable.</p>
+ <span class="APPLICATION">Privoxy</span> executable. The name and
+ number of configuration files has changed from previous versions, and
+ is subject to change as development progresses.</p>
<p>The installed defaults provide a reasonable starting point, though
some settings may be aggressive by some standards. For the time being,
"QUOTE">"wake up"</span> requests must obviously be sent to the
<span class="emphasis"><i class="EMPHASIS">old</i></span> listening
address.</p>
+
+ <p>While under development, the configuration content is subject to
+ change. The below documentation may not be accurate by the time you
+ read this. Also, what constitutes a <span class=
+ "QUOTE">"default"</span> setting, may change, so please check all your
+ configuration files on important issues.</p>
</div>
</div>
Requests</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Privoxy's Template Files" href=
"templates.html">
<link rel="NEXT" title="Privoxy Copyright, License and History" href=
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
<title>Privoxy Copyright, License and History</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title=
"Contacting the Developers, Bug Reporting and Feature Requests" href=
"contact.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
"CITETITLE">GNU General Public License</i>.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN5542" id="AEN5542">12.1. License</a></h2>
+ <h2 class="SECT2"><a name="AEN5621" id="AEN5621">12.1. License</a></h2>
<p><span class="APPLICATION">Privoxy</span> is free software; you can
redistribute it and/or modify it under the terms of the <i class=
<div class="SECT2">
<h2 class="SECT2"><a name="HISTORY" id="HISTORY">12.2. History</a></h2>
- <p>A long time ago, there was the <a href=
- "http://www.junkbusters.com/ijb.html" target="_top"><span class=
- "APPLICATION">Internet Junkbuster</span></a>, by Anonymous Coders and
- <a href="http://www.junkbusters.com/" target="_top">Junkbusters
- Corporation</a>. This saved many users a lot of pain in the early days
- of web advertising and user tracking.</p>
+ <p>A long time ago, there was the <span class="APPLICATION">Internet
+ Junkbuster</span>, by Anonymous Coders and Junkbusters Corporation.
+ This saved many users a lot of pain in the early days of web
+ advertising and user tracking.</p>
<p>But the web, its protocols and standards, and with it, the
techniques for forcing ads on users, give up autonomy over their
browsing, and for tracking them, keeps evolving. Unfortunately, the
<span class="APPLICATION">Internet Junkbuster</span> did not. Version
- 2.0.2, published in 1998, was (and is) the last official <a href=
- "http://www.junkbusters.com/ijbdist.html#release" target=
- "_top">release</a> available from <a href="http://www.junkbusters.com"
- target="_top">Junkbusters Corporation</a>. Fortunately, it had been
- released under the GNU <a href=
- "http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target=
- "_top">GPL</a>, which allowed further development by others.</p>
+ 2.0.2, published in 1998, was the last official release, available from
+ Junkbusters Corporation. Fortunately, it had been released under the
+ GNU <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html"
+ target="_top">GPL</a>, which allowed further development by others.</p>
<p>So Stefan Waldherr started maintaining an improved version of the
software, to which eventually a number of people contributed patches.
<p>The result of this is <span class="APPLICATION">Privoxy</span>,
whose first stable version, 3.0, was released August, 2002.</p>
+
+ <p>As of 2012 the Junkbusters Corporation's website
+ (http://www.junkbusters.com/) has been shut down, but Privoxy is still
+ actively maintained.</p>
</div>
<div class="SECT2">
David Schmidt, developer<br>
Hal Burgiss<br>
Lee Rian<br>
- Roland Rosenfeld</p>
+ Roland Rosenfeld<br>
+ Ian Silvester</p>
<p>Former Privoxy Team Members:</p>
Markus Elfring<br>
Dean Gaudet<br>
Stephen Gildea<br>
+ Lizik Grelier<br>
Daniel Griscom<br>
Felix Gröbert<br>
Jeff H.<br>
Stefan Huehner<br>
Peter Hyman<br>
Derek Jennings<br>
+ Andrew Jones<br>
+ Julien Joubert<br>
Petr Kadlec<br>
+ Steven Kolins<br>
David Laight<br>
Bert van Leeuwen<br>
Don Libes<br>
Roberto Ragusa<br>
Félix Rauch<br>
Maynard Riley<br>
+ Andreas Rutkauskas<br>
Chung-chieh Shan<br>
Spinor S.<br>
Bart Schelstraete<br>
<title>Filter Files</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Actions Files" href="actions-file.html">
<link rel="NEXT" title="Privoxy's Template Files" href="templates.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
started.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN5060" id="AEN5060">9.1. Filter File
+ <h2 class="SECT2"><a name="AEN5139" id="AEN5139">9.1. Filter File
Tutorial</a></h2>
<p>Now, let's complete our <span class="QUOTE">"foo"</span> content
wherever you would also use the cookie crunch actions.</p>
</dd>
- <dt><span class="emphasis"><i class="EMPHASIS">refresh
- tags</i></span></dt>
+ <dt><span class="emphasis"><i class=
+ "EMPHASIS">refresh-tags</i></span></dt>
<dd>
<p>Disable any refresh tags if the interval is greater than nine
<html>
<head>
- <title>Privoxy 3.0.19 User Manual</title>
+ <title>Privoxy 3.0.20 User Manual</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
<link rel="NEXT" title="Introduction" href="introduction.html">
"#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
- <h1 class="TITLE"><a name="AEN2" id="AEN2">Privoxy 3.0.19 User
+ <h1 class="TITLE"><a name="AEN2" id="AEN2">Privoxy 3.0.20 User
Manual</a></h1>
<p class="PUBDATE"><sub><a href="copyright.html">Copyright</a> ©
2001-2011 by <a href="http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: user-manual.sgml,v 2.146 2011/12/26 17:05:40
+ <p class="PUBDATE">$Id: user-manual.sgml,v 2.150 2012/09/26 15:20:54
fabiankeil Exp $<br></p>
<div>
OS X</a></dt>
<dt>2.1.7. <a href=
- "installation.html#INSTALLATION-AMIGA">AmigaOS</a></dt>
+ "installation.html#OS-X-INSTALL-FROM-PACKAGE">Installation
+ from ready-built package</a></dt>
<dt>2.1.8. <a href=
- "installation.html#INSTALLATION-TBZ">FreeBSD</a></dt>
+ "installation.html#OS-X-INSTALL-FROM-SOURCE">Installation
+ from source</a></dt>
<dt>2.1.9. <a href=
+ "installation.html#INSTALLATION-AMIGA">AmigaOS</a></dt>
+
+ <dt>2.1.10. <a href=
+ "installation.html#INSTALLATION-TBZ">FreeBSD</a></dt>
+
+ <dt>2.1.11. <a href=
"installation.html#INSTALLATTION-GENTOO">Gentoo</a></dt>
</dl>
</dd>
<dd>
<dl>
- <dt>6.1. <a href="configuration.html#AEN1090">Controlling Privoxy
+ <dt>6.1. <a href="configuration.html#AEN1107">Controlling Privoxy
with Your Web Browser</a></dt>
<dt>6.2. <a href="configuration.html#CONFOVERVIEW">Configuration
"config.html#KEEP-ALIVE-TIMEOUT">keep-alive-timeout</a></dt>
<dt>7.6.5. <a href=
- "config.html#DEFAULT-SERVER-TIMEOUT">default-server-timeout</a></dt>
+ "config.html#TOLERATE-PIPELINING">tolerate-pipelining</a></dt>
<dt>7.6.6. <a href=
- "config.html#CONNECTION-SHARING">connection-sharing</a></dt>
+ "config.html#DEFAULT-SERVER-TIMEOUT">default-server-timeout</a></dt>
<dt>7.6.7. <a href=
- "config.html#SOCKET-TIMEOUT">socket-timeout</a></dt>
+ "config.html#CONNECTION-SHARING">connection-sharing</a></dt>
<dt>7.6.8. <a href=
- "config.html#MAX-CLIENT-CONNECTIONS">max-client-connections</a></dt>
+ "config.html#SOCKET-TIMEOUT">socket-timeout</a></dt>
<dt>7.6.9. <a href=
- "config.html#HANDLE-AS-EMPTY-DOC-RETURNS-OK">handle-as-empty-doc-returns-ok</a></dt>
+ "config.html#MAX-CLIENT-CONNECTIONS">max-client-connections</a></dt>
<dt>7.6.10. <a href=
- "config.html#ENABLE-COMPRESSION">enable-compression</a></dt>
+ "config.html#HANDLE-AS-EMPTY-DOC-RETURNS-OK">handle-as-empty-doc-returns-ok</a></dt>
<dt>7.6.11. <a href=
+ "config.html#ENABLE-COMPRESSION">enable-compression</a></dt>
+
+ <dt>7.6.12. <a href=
"config.html#COMPRESSION-LEVEL">compression-level</a></dt>
+
+ <dt>7.6.13. <a href=
+ "config.html#CLIENT-HEADER-ORDER">client-header-order</a></dt>
</dl>
</dd>
<dd>
<dl>
- <dt>8.1. <a href="actions-file.html#AEN2879">Finding the Right
+ <dt>8.1. <a href="actions-file.html#AEN2954">Finding the Right
Mix</a></dt>
- <dt>8.2. <a href="actions-file.html#AEN2886">How to Edit</a></dt>
+ <dt>8.2. <a href="actions-file.html#AEN2961">How to Edit</a></dt>
<dt>8.3. <a href="actions-file.html#ACTIONS-APPLY">How Actions
are Applied to Requests</a></dt>
<dd>
<dl>
- <dt>8.4.1. <a href="actions-file.html#AEN2998">The Domain
+ <dt>8.4.1. <a href="actions-file.html#AEN3073">The Domain
Pattern</a></dt>
- <dt>8.4.2. <a href="actions-file.html#AEN3074">The Path
+ <dt>8.4.2. <a href="actions-file.html#AEN3149">The Path
Pattern</a></dt>
<dt>8.4.3. <a href="actions-file.html#TAG-PATTERN">The Tag
"actions-file.html#SET-IMAGE-BLOCKER">set-image-blocker</a></dt>
<dt>8.5.34. <a href=
- "actions-file.html#AEN4706">Summary</a></dt>
+ "actions-file.html#AEN4785">Summary</a></dt>
</dl>
</dd>
<dd>
<dl>
<dt>8.7.1. <a href=
- "actions-file.html#AEN4770">match-all.action</a></dt>
+ "actions-file.html#AEN4849">match-all.action</a></dt>
<dt>8.7.2. <a href=
- "actions-file.html#AEN4792">default.action</a></dt>
+ "actions-file.html#AEN4871">default.action</a></dt>
<dt>8.7.3. <a href=
- "actions-file.html#AEN4905">user.action</a></dt>
+ "actions-file.html#AEN4984">user.action</a></dt>
</dl>
</dd>
</dl>
<dd>
<dl>
- <dt>9.1. <a href="filter-file.html#AEN5060">Filter File
+ <dt>9.1. <a href="filter-file.html#AEN5139">Filter File
Tutorial</a></dt>
<dt>9.2. <a href="filter-file.html#PREDEFINED-FILTERS">The
<dd>
<dl>
- <dt>12.1. <a href="copyright.html#AEN5542">License</a></dt>
+ <dt>12.1. <a href="copyright.html#AEN5621">License</a></dt>
<dt>12.2. <a href="copyright.html#HISTORY">History</a></dt>
<dt>14.1. <a href="appendix.html#REGEX">Regular
Expressions</a></dt>
- <dt>14.2. <a href="appendix.html#AEN5795">Privoxy's Internal
+ <dt>14.2. <a href="appendix.html#AEN5865">Privoxy's Internal
Pages</a></dt>
<dd>
<title>Installation</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Introduction" href="introduction.html">
<link rel="NEXT" title="What's New in this Release" href="whatsnew.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
"INSTALLATION-PACK-RPM">2.1.1. Red Hat and Fedora RPMs</a></h3>
<p>RPMs can be installed with <tt class="LITERAL">rpm -Uvh
- privoxy-3.0.19-1.rpm</tt>, and will use <tt class=
+ privoxy-3.0.20-1.rpm</tt>, and will use <tt class=
"FILENAME">/etc/privoxy</tt> for the location of configuration
files.</p>
<p>If you have problems with failed dependencies, try rebuilding the
SRC RPM: <tt class="LITERAL">rpm --rebuild
- privoxy-3.0.19-1.src.rpm</tt>. This will use your locally installed
+ privoxy-3.0.20-1.src.rpm</tt>. This will use your locally installed
libraries and RPM version.</p>
<p>Also note that if you have a <span class=
<h3 class="SECT3"><a name="INSTALLATION-MAC" id=
"INSTALLATION-MAC">2.1.6. Mac OS X</a></h3>
- <p>Unzip the downloaded file (you can either double-click on the zip
- file icon from the Finder, or from the desktop if you downloaded it
- there). Then, double-click on the package installer icon and follow
- the installation process.</p>
+ <p>Installation instructions for the OS X platform depend upon
+ whether you downloaded a ready-built installation package (.pkg or
+ .mpkg) or have downloaded the source code.</p>
+ </div>
+
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="OS-X-INSTALL-FROM-PACKAGE" id=
+ "OS-X-INSTALL-FROM-PACKAGE">2.1.7. Installation from ready-built
+ package</a></h4>
+
+ <p>The downloaded file will either be a .pkg (for OS X 10.5 upwards)
+ or a bzipped .mpkg file (for OS X 10.4). The former can be
+ double-clicked as is and the installation will start; double-clicking
+ the latter will unzip the .mpkg file which can then be double-clicked
+ to commence the installation.</p>
+
+ <p>The privoxy service will automatically start after a successful
+ installation (and thereafter every time your computer starts up)
+ however you will need to configure your web browser(s) to use it. To
+ do so, configure them to use a proxy for HTTP and HTTPS at the
+ address 127.0.0.1:8118.</p>
+
+ <p>To prevent the privoxy service from automatically starting when
+ your computer starts up, remove or rename the file <tt class=
+ "LITERAL">/Library/LaunchDaemons/org.ijbswa.privoxy.plist</tt> (on OS
+ X 10.5 and higher) or the folder named <tt class=
+ "LITERAL">/Library/StartupItems/Privoxy</tt> (on OS X 10.4
+ 'Tiger').</p>
+
+ <p>To manually start or stop the privoxy service, use the scripts
+ startPrivoxy.sh and stopPrivoxy.sh supplied in /Applications/Privoxy.
+ They must be run from an administrator account, using sudo.</p>
+
+ <p>To uninstall, run /Applications/Privoxy/uninstall.command as sudo
+ from an administrator account.</p>
+ </div>
+
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="OS-X-INSTALL-FROM-SOURCE" id=
+ "OS-X-INSTALL-FROM-SOURCE">2.1.8. Installation from source</a></h4>
+
+ <p>To build and install the Privoxy source code on OS X you will need
+ to obtain the macsetup module from the Privoxy Sourceforge CVS
+ repository (refer to Sourceforge help for details of how to set up a
+ CVS client to have read-only access to the repository). This module
+ contains scripts that leverage the usual open-source tools (available
+ as part of Apple's free of charge Xcode distribution or via the usual
+ open-source software package managers for OS X (MacPorts, Homebrew,
+ Fink etc.) to build and then install the privoxy binary and
+ associated files. The macsetup module's README file contains complete
+ instructions for its use.</p>
<p>The privoxy service will automatically start after a successful
- installation (in addition to every time your computer starts up). To
- prevent the privoxy service from automatically starting when your
- computer starts up, remove or rename the folder named <tt class=
- "LITERAL">/Library/StartupItems/Privoxy</tt>.</p>
+ installation (and thereafter every time your computer starts up)
+ however you will need to configure your web browser(s) to use it. To
+ do so, configure them to use a proxy for HTTP and HTTPS at the
+ address 127.0.0.1:8118.</p>
+
+ <p>To prevent the privoxy service from automatically starting when
+ your computer starts up, remove or rename the file <tt class=
+ "LITERAL">/Library/LaunchDaemons/org.ijbswa.privoxy.plist</tt> (on OS
+ X 10.5 and higher) or the folder named <tt class=
+ "LITERAL">/Library/StartupItems/Privoxy</tt> (on OS X 10.4
+ 'Tiger').</p>
<p>To manually start or stop the privoxy service, use the Privoxy
- Utility for Mac OS X. This application controls the privoxy service
- (e.g. starting and stopping the service as well as uninstalling the
- software).</p>
+ Utility for Mac OS X (also part of the macsetup module). This
+ application can start and stop the privoxy service and display its
+ log and configuration files.</p>
+
+ <p>To uninstall, run the macsetup module's uninstall.sh as sudo from
+ an administrator account.</p>
</div>
<div class="SECT3">
<h3 class="SECT3"><a name="INSTALLATION-AMIGA" id=
- "INSTALLATION-AMIGA">2.1.7. AmigaOS</a></h3>
+ "INSTALLATION-AMIGA">2.1.9. AmigaOS</a></h3>
<p>Copy and then unpack the <tt class="FILENAME">lha</tt> archive to
a suitable location. All necessary files will be installed into
<div class="SECT3">
<h3 class="SECT3"><a name="INSTALLATION-TBZ" id=
- "INSTALLATION-TBZ">2.1.8. FreeBSD</a></h3>
+ "INSTALLATION-TBZ">2.1.10. FreeBSD</a></h3>
<p>Privoxy is part of FreeBSD's Ports Collection, you can build and
install it with <tt class="LITERAL">cd /usr/ports/www/privoxy; make
<div class="SECT3">
<h3 class="SECT3"><a name="INSTALLATTION-GENTOO" id=
- "INSTALLATTION-GENTOO">2.1.9. Gentoo</a></h3>
+ "INSTALLATTION-GENTOO">2.1.11. Gentoo</a></h3>
<p>Gentoo source packages (Ebuilds) for <span class=
"APPLICATION">Privoxy</span> are contained in the Gentoo Portage Tree
<p>Configuration files are in <tt class="FILENAME">/etc/privoxy</tt>,
the documentation is in <tt class=
- "FILENAME">/usr/share/doc/privoxy-3.0.19</tt> and the Log directory
+ "FILENAME">/usr/share/doc/privoxy-3.0.20</tt> and the Log directory
is in <tt class="FILENAME">/var/log/privoxy</tt>.</p>
</div>
</div>
<tr>
<td>
<pre class="SCREEN">
- tar xzvf privoxy-3.0.19-stable-src.tar.gz
- cd privoxy-3.0.19-stable
+ tar xzvf privoxy-3.0.20-beta-src.tar.gz
+ cd privoxy-3.0.20-beta
</pre>
</td>
</tr>
<title>Introduction</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
- <link rel="PREVIOUS" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
+ <link rel="PREVIOUS" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="NEXT" title="Installation" href="installation.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
<h1 class="SECT1"><a name="INTRODUCTION" id="INTRODUCTION">1.
Introduction</a></h1>
- <p>This documentation is included with the current stable version of
- <span class="APPLICATION">Privoxy</span>, v.3.0.19.</p>
+ <p>This documentation is included with the current UNRELEASED version of
+ <span class="APPLICATION">Privoxy</span>, v.3.0.20, and is mostly
+ complete at this point. The most up to date reference for the time being
+ is still the comments in the source files and in the individual
+ configuration files. Development of a new version is currently nearing
+ completion, and includes significant changes and enhancements over
+ earlier versions.</p>
+
+ <p>Since this is a UNRELEASED version, not all new features are well
+ tested. This documentation may be slightly out of sync as a result
+ (especially with CVS sources). And there <span class="emphasis"><i class=
+ "EMPHASIS">may be</i></span> bugs, though hopefully not many!</p>
<div class="SECT2">
<h2 class="SECT2"><a name="FEATURES" id="FEATURES">1.1.
<p>In addition to the core features of ad blocking and <a href=
"http://en.wikipedia.org/wiki/Browser_cookie" target="_top">cookie</a>
management, <span class="APPLICATION">Privoxy</span> provides many
- supplemental features, that give the end-user more control, more
- privacy and more freedom:</p>
+ supplemental features, some of them currently under development, that
+ give the end-user more control, more privacy and more freedom:</p>
<ul>
<li>
</tr>
<tr>
- <td width="33%" align="left" valign="top">Privoxy 3.0.19 User
+ <td width="33%" align="left" valign="top">Privoxy 3.0.20 User
Manual</td>
<td width="34%" align="center" valign="top"> </td>
<title>Quickstart to Using Privoxy</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="What's New in this Release" href=
"whatsnew.html">
<link rel="NEXT" title="Starting Privoxy" href="startup.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
"GUIBUTTON">Edit</span>"</span>:</p>
<div class="FIGURE">
- <a name="AEN844" id="AEN844"></a>
+ <a name="AEN861" id="AEN861"></a>
<p><b>Figure 1. Actions Files in Use</b></p>
<title>See Also</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Privoxy Copyright, License and History" href=
"copyright.html">
<link rel="NEXT" title="Appendix" href="appendix.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
</tbody>
</table>
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ht/en/cookies.html" target=
- "_top">http://www.junkbusters.com/ht/en/cookies.html</a>, an
- explanation how cookies are used to track web users.</td>
- </tr>
- </tbody>
- </table>
-
- <table border="0">
- <tbody>
- <tr>
- <td><a href="http://www.junkbusters.com/ijb.html" target=
- "_top">http://www.junkbusters.com/ijb.html</a>, the original
- Internet Junkbuster.</td>
- </tr>
- </tbody>
- </table>
-
<table border="0">
<tbody>
<tr>
<title>Starting Privoxy</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Quickstart to Using Privoxy" href=
"quickstart.html">
<link rel="NEXT" title="Privoxy Configuration" href="configuration.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
protocols.</p>
<div class="FIGURE">
- <a name="AEN899" id="AEN899"></a>
+ <a name="AEN916" id="AEN916"></a>
<p><b>Figure 2. Proxy Configuration Showing Mozilla/Netscape HTTP and
HTTPS (SSL) Settings</b></p>
only HTTP and HTTPS (SSL)!</p>
<div class="FIGURE">
- <a name="AEN944" id="AEN944"></a>
+ <a name="AEN961" id="AEN961"></a>
<p><b>Figure 3. Proxy Configuration Showing Internet Explorer HTTP and
HTTPS (Secure) Settings</b></p>
<title>Privoxy's Template Files</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Filter Files" href="filter-file.html">
<link rel="NEXT" title=
"Contacting the Developers, Bug Reporting and Feature Requests" href=
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
<title>What's New in this Release</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.19 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
<link rel="PREVIOUS" title="Installation" href="installation.html">
<link rel="NEXT" title="Quickstart to Using Privoxy" href=
"quickstart.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
</tr>
<tr>
projects / privoxy.git / commitdiff