Copyright © 2001, 2002 by Privoxy Developers
-$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $
+$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $
The developer manual provides guidance on coding, testing, packaging,
development. It is mandatory (and helpful!) reading for anyone who wants to
join the team.
-You can find the latest version of the this manual at http://www.privoxy.org/
-developer-manual/. Please see the Contact section on how to contact the
-developers.
+Please note that this document is constantly evolving. This copy represents the
+state at the release of version 2.9.20. You can find the latest version of the
+this manual at http://www.privoxy.org/developer-manual/. Please see the Contact
+section on how to contact the developers.
-------------------------------------------------------------------------------
Table of Contents
* Before changing things on CVS, make sure that your changes are in line with
the team's general consensus on what should be done (see below).
+ * Don't commit into the stable branch, unless immediately before a new
+ release. (See Version Numbers below for details.) Collect your changes on
+ the patches tracker instead.
+
-------------------------------------------------------------------------------
2.3. Discussing Changes First
modular stylesheets (or comparable alternatives), and either jade or openjade
(recommended) installed in order to build docs from source. Currently there is
user-manual, FAQ, and, of course this, the developer-manual in this format. The
-README, AUTHORS privoxy.1 (man page) files are also now maintained as Docbook
-SGML. The finished files are all in the top-level source directory are
-generated files! Also, index.html, the Privoxy home page, is maintained as
-SGML. DO NOT edit these directly. Edit the SGML source, or contact someone
-involved in the documentation (at present Stefan and Hal).
+README, AUTHORS privoxy.1 (man page), and config files are also now maintained
+as Docbook SGML. These files, when built, in the top-level source directory are
+generated files! Also, the Privoxy index.html (and a variation on this file,
+privoxy-index.html, meant for inclusion with doc packages), are maintained as
+SGML as well. DO NOT edit these directly. Edit the SGML source, or contact
+someone involved in the documentation (at present Stefan and Hal).
+
+config requires some special handling. The reason it is maintained this way is
+so that the extensive comments in the file mirror those in user-manual. But the
+conversion process requires going from SGML to HTML to text to special
+formatting required for the embedded comments. Some of this does not survive so
+well. Especially some of the examples that are longer than 80 characters. The
+build process for this file outputs to config.new, which should be reviewed for
+errors and mis-formatting. Once satisfied that it is correct, then it should be
+hand copied to config.
Other, less formal documents (e.g. LICENSE, INSTALL) are maintained as plain
text files in the top-level source directory. At least for the time being.
* Commonly used "internal entities":
- p-version: the Privoxy version string, e.g. "2.9.18".
+ p-version: the Privoxy version string, e.g. "2.9.20".
p-status: the project status, either "alpha", "beta", or "stable".
p-not-stable: use to conditionally include text in "not stable" releases
(e.g. "beta").
4.8. Addendum: Template for files and function comment blocks:
Example for file comments:
-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $";
-/*********************************************************************
- *
- * File : $Source$
- *
- * Purpose : (Fill me in with a good description!)
- *
- * Copyright : Written by and Copyright (C) 2001 the SourceForge
- * Privoxy team. http://www.privoxy.org/
- *
- * Based on the Internet Junkbuster originally written
- * by and Copyright (C) 1997 Anonymous Coders and
- * Junkbusters Corporation. http://www.junkbusters.com
- *
- * This program is free software; you can redistribute it
- * and/or modify it under the terms of the GNU General
- * Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at
- * your option) any later version.
- *
- * This program is distributed in the hope that it will
- * be useful, but WITHOUT ANY WARRANTY; without even the
- * implied warranty of MERCHANTABILITY or FITNESS FOR A
- * PARTICULAR PURPOSE. See the GNU General Public
- * License for more details.
- *
- * The GNU General Public License should be included with
- * this file. If not, you can view it at
- * http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc., 59
- * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
- *
- * Revisions :
- * $Log$
- *
- *********************************************************************/
-
-
-#include "config.h"
-
- ...necessary include files for us to do our work...
-
-const char FILENAME_h_rcs[] = FILENAME_H_VERSION;
+const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $";
+/*********************************************************************
+ *
+ * File : $Source$
+ *
+ * Purpose : (Fill me in with a good description!)
+ *
+ * Copyright : Written by and Copyright (C) 2001 the SourceForge
+ * Privoxy team. http://www.privoxy.org/
+ *
+ * Based on the Internet Junkbuster originally written
+ * by and Copyright (C) 1997 Anonymous Coders and
+ * Junkbusters Corporation. http://www.junkbusters.com
+ *
+ * This program is free software; you can redistribute it
+ * and/or modify it under the terms of the GNU General
+ * Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at
+ * your option) any later version.
+ *
+ * This program is distributed in the hope that it will
+ * be useful, but WITHOUT ANY WARRANTY; without even the
+ * implied warranty of MERCHANTABILITY or FITNESS FOR A
+ * PARTICULAR PURPOSE. See the GNU General Public
+ * License for more details.
+ *
+ * The GNU General Public License should be included with
+ * this file. If not, you can view it at
+ * http://www.gnu.org/copyleft/gpl.html
+ * or write to the Free Software Foundation, Inc., 59
+ * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ *
+ * Revisions :
+ * $Log$
+ *
+ *********************************************************************/
+
+
+#include "config.h"
+
+ ...necessary include files for us to do our work...
+
+const char FILENAME_h_rcs[] = FILENAME_H_VERSION;
Note: This declares the rcs variables that should be added to the
"show-proxy-args" page. If this is a brand new creation by you, you are free to
can.
Example for file header comments:
-#ifndef _FILENAME_H
-#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $"
-/*********************************************************************
- *
- * File : $Source$
- *
- * Purpose : (Fill me in with a good description!)
- *
- * Copyright : Written by and Copyright (C) 2001 the SourceForge
- * Privoxy team. http://www.privoxy.org/
- *
- * Based on the Internet Junkbuster originally written
- * by and Copyright (C) 1997 Anonymous Coders and
- * Junkbusters Corporation. http://www.junkbusters.com
- *
- * This program is free software; you can redistribute it
- * and/or modify it under the terms of the GNU General
- * Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at
- * your option) any later version.
- *
- * This program is distributed in the hope that it will
- * be useful, but WITHOUT ANY WARRANTY; without even the
- * implied warranty of MERCHANTABILITY or FITNESS FOR A
- * PARTICULAR PURPOSE. See the GNU General Public
- * License for more details.
- *
- * The GNU General Public License should be included with
- * this file. If not, you can view it at
- * http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc., 59
- * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
- *
- * Revisions :
- * $Log$
- *
- *********************************************************************/
-
-
-#include "project.h"
-
-#ifdef __cplusplus
-extern "C" {
-#endif
-
- ... function headers here ...
-
-
-/* Revision control strings from this header and associated .c file */
-extern const char FILENAME_rcs[];
-extern const char FILENAME_h_rcs[];
-
-
-#ifdef __cplusplus
-} /* extern "C" */
-#endif
-
-#endif /* ndef _FILENAME_H */
-
-/*
- Local Variables:
- tab-width: 3
- end:
-*/
+#ifndef _FILENAME_H
+#define _FILENAME_H
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $"
+/*********************************************************************
+ *
+ * File : $Source$
+ *
+ * Purpose : (Fill me in with a good description!)
+ *
+ * Copyright : Written by and Copyright (C) 2001 the SourceForge
+ * Privoxy team. http://www.privoxy.org/
+ *
+ * Based on the Internet Junkbuster originally written
+ * by and Copyright (C) 1997 Anonymous Coders and
+ * Junkbusters Corporation. http://www.junkbusters.com
+ *
+ * This program is free software; you can redistribute it
+ * and/or modify it under the terms of the GNU General
+ * Public License as published by the Free Software
+ * Foundation; either version 2 of the License, or (at
+ * your option) any later version.
+ *
+ * This program is distributed in the hope that it will
+ * be useful, but WITHOUT ANY WARRANTY; without even the
+ * implied warranty of MERCHANTABILITY or FITNESS FOR A
+ * PARTICULAR PURPOSE. See the GNU General Public
+ * License for more details.
+ *
+ * The GNU General Public License should be included with
+ * this file. If not, you can view it at
+ * http://www.gnu.org/copyleft/gpl.html
+ * or write to the Free Software Foundation, Inc., 59
+ * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ *
+ * Revisions :
+ * $Log$
+ *
+ *********************************************************************/
+
+
+#include "project.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+ ... function headers here ...
+
+
+/* Revision control strings from this header and associated .c file */
+extern const char FILENAME_rcs[];
+extern const char FILENAME_h_rcs[];
+
+
+#ifdef __cplusplus
+} /* extern "C" */
+#endif
+
+#endif /* ndef _FILENAME_H */
+
+/*
+ Local Variables:
+ tab-width: 3
+ end:
+*/
Example for function comments:
/*********************************************************************
last minute changes.
* Increment the version number (point from odd to even in development
- branches!) in configure.in.
+ branches!) in configure.in. (RPM spec files will need to be incremented as
+ well.)
* If default.action has changed since last release (i.e. software release or
standalone actions file release), bump up its version info to A.B in this
Then change the version info in doc/webserver/actions/index.php, line:
'$required_actions_file_version = "A.B";'
- * If the HTML documentation is not in sync with the SGML sources you need to
- regenerate and upload it to the webserver. (If in doubt, just do it.) See
- the Section "Updating the webserver" in this manual for details.
+ * All documentation should be rebuild after the version bump. Finished docs
+ should be then be committed to CVS (for those without the ability to build
+ these). Some docs may require rather obscure processing tools. config, the
+ man page (and the html version of the man page), and the PDF docs fall in
+ this category. REAMDE, the man page, AUTHORS, and config should all also be
+ committed to CVS for other packageers. The formal docs should be uploaded
+ to the webserver. See the Section "Updating the webserver" in this manual
+ for details.
+
+ * All developers should look at the ChangeLog and make sure noteworthy
+ changes are referenced.
* Commit all files that were changed in the above steps!
For all types of packages, including the source tarball, you must make sure
that you build from clean sources by exporting the right version from CVS into
-an empty directory:.
+an empty directory (just press return when asked for a password):
mkdir dist # delete or choose different name if it already exists
cd dist
please add any notes that you know are important for your platform (or
contact one of the doc maintainers to do this if you can't).
+ * Packagers should do a "clean" install of their package after building it.
+ So any previous installs should be removed first to ensure the integrity of
+ the newly built package. Then run the package for a while to make sure
+ there are no obvious problems, before uploading.
+
-------------------------------------------------------------------------------
6.3.2. Source Tarball
directory. (See "Building and releasing packages" above). Then add a log entry
to debian/changelog, if it is not already there, for example by running:
- debchange -v 2.9.18-beta-1 "New upstream version"
+ debchange -v 2.9.20-beta-1 "New upstream version"
Then, run:
dpkg-buildpackage -rfakeroot -us -uc -b
-This will create ../privoxy_2.9.18-beta-1_i386.deb which can be uploaded. To
+This will create ../privoxy_2.9.20-beta-1_i386.deb which can be uploaded. To
upload the package to Sourceforge, simply issue
make debian-upload
group_id=11118, making sure you are logged in. Find your target platform in the
second column, and click Add Release. You will then need to create a new
release for your package, using the format of $VERSION ($CODE_STATUS), e.g.
-2.9.18 (beta).
+2.9.20 (beta).
Now just follow the prompts. Be sure to add any appropriate Release notes. You
should see your freshly uploaded packages in "Step 2. Add Files To This
Copyright © 2001, 2002 by Privoxy Developers
-$Id: faq.sgml,v 1.61.2.11 2002/08/06 08:54:03 oes Exp $
+$Id: faq.sgml,v 1.61.2.15 2002/08/10 11:34:22 oes Exp $
-This FAQ gives quick answers to frequently asked questions about Privoxy . It
+This FAQ gives quick answers to frequently asked questions about Privoxy. It
can't and doesn't replace the User Manual.
Privoxy is a web proxy with advanced filtering capabilities for protecting
Privoxy is based on Internet Junkbuster (tm).
-You can find the latest version of the document at http://www.privoxy.org/faq/.
-Please see the Contact section if you want to contact the developers.
+Please note that this document is constantly evolving. This copy represents the
+state at the release of version 2.9.20. You can find the latest version of the
+document at http://www.privoxy.org/faq/. Please see the Contact section if you
+want to contact the developers.
-------------------------------------------------------------------------------
Table of Contents
2.5. What is the proxy address of Privoxy?
2.6. I just installed Privoxy, and nothing is happening. All the ads are
there. What's wrong?
- 2.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
- uninstall it. Now the finder tells me I don't have sufficient
- privileges to empty the trash.
3. Configuration
5.5. I cannot connect to any FTP sites. Privoxy seems to be blocking me.
5.6. In Mac OSX, I can't configure Microsoft Internet Explorer to use
Privoxy as the HTTP proxy.
+ 5.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
+ uninstall it. Now the finder tells me I don't have sufficient
+ privileges to empty the trash.
6. Contacting the developers, Bug Reporting and Feature Requests
up correctly, or that Privoxy is not running at all. Check the log file.
-------------------------------------------------------------------------------
-2.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
-uninstall it. Now the finder tells me I don't have sufficient privileges to
-empty the trash.
-
-Privoxy is installed with root permissions. When you drag the Privoxy folder to
-the trash, the general user does not have (as the Finder says) sufficient
-privileges to delete it. Unfortunately, the finder does not offer a way to
-enter the administrator password in order to prove you do in fact own this
-computer. To fix this situation, open the Terminal application and carefully
-enter the following commands:
-
- cd ~
- cd .Trash
- sudo rm -rf Privoxy
-
-The trash may still appear full after this command; emptying the trash from the
-desktop should make it appear empty again.
-
-+-----------------------------------------------------------------------------+
-| Warning |
-+-----------------------------------------------------------------------------+
-|Be extra-sure to enter the commands EXACTLY as shown above. Removing files |
-|recusively with administrator priviledges (as happens with sudo rm -rf is |
-|serious business and even small typos can have devasting effects! |
-+-----------------------------------------------------------------------------+
--------------------------------------------------------------------------------
-
3. Configuration
3.1. Where can I get updated Actions Files?
Note that the built-in URLs from earlier versions of Junkbuster / Privoxy,
http://example.com/show-proxy-args and http://i.j.b/, are no longer supported.
If you still use such an old version, you should really consider upgrading to
-2.9.18.
+2.9.20.
-------------------------------------------------------------------------------
4.4. Do you still maintain the blocklists?
should reflect these values.
-------------------------------------------------------------------------------
+5.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
+uninstall it. Now the finder tells me I don't have sufficient privileges to
+empty the trash.
+
+Just dragging the Privoxy folder to the trash is not enough to delete it.
+Privoxy supplies an uninstall.command file that takes care of these details.
+Open the trash, drag the uninstall.command file out of the trash and
+double-click on it. You will be prompted for confirmation and the
+administration password.
+
+The trash may still appear full after this command; emptying the trash from the
+desktop should make it appear empty again.
+-------------------------------------------------------------------------------
+
6. Contacting the developers, Bug Reporting and Feature Requests
We value your feedback. In fact, we rely on it to improve Privoxy and its
-Privoxy 2.9.18 User Manual
+Privoxy 2.9.20 User Manual
Copyright © 2001, 2002 by Privoxy Developers
-$Id: user-manual.sgml,v 1.123.2.14 2002/08/06 09:16:13 oes Exp $
+$Id: user-manual.sgml,v 1.123.2.16 2002/08/09 19:20:54 david__schmidt Exp $
The User Manual gives users information on how to install, configure and use
1. Introduction
This documentation is included with the current beta version of Privoxy,
-v.2.9.18, and is mostly complete at this point. The most up to date reference
+v.2.9.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 version 3.0 is currently nearing
completion, and includes many significant changes and enhancements over earlier
2.1.1. Red Hat, SuSE and Conectiva RPMs
-RPMs can be installed with rpm -Uvh privoxy-2.9.18-1.rpm, and will use /etc/
+RPMs can be installed with rpm -Uvh privoxy-2.9.20-1.rpm, and will use /etc/
privoxy for the location of configuration files.
Note that on Red Hat, Privoxy will not be automatically started on system boot.
that SuSE will automatically start Privoxy in the boot process.
If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm
---rebuild privoxy-2.9.18-1.src.rpm. This will use your locally installed
+--rebuild privoxy-2.9.20-1.src.rpm. This will use your locally installed
libraries and RPM version.
Also note that if you have a Junkbuster RPM installed on your system, you need
2.1.2. Debian
-DEBs can be installed with dpkg -i privoxy_2.9.18-1.deb, and will use /etc/
+DEBs can be installed with dpkg -i privoxy_2.9.20-1.deb, and will use /etc/
privoxy for the location of configuration files.
-------------------------------------------------------------------------------
2.1.6. Mac OSX
-Unzip the downloaded package (you can either double-click on the file in the
-finder, or on the desktop if you downloaded it there). The Privoxy.pkg package
-should appear after unzipping. Then, double-click on that Privoxy.pkg package
-installer icon and follow the installation process. Privoxy will be installed
-in the folder /Library/Privoxy. It will run automatically whenever you start
-up. To prevent it from running automatically, remove or rename the folder /
-Library/StartupItems/Privoxy.
+Unzip the downloaded file (you can either double-click on the file from the
+finder, or from the desktop if you downloaded it there). Then, double-click on
+the package installer icon named Privoxy.pkg and follow the installation
+process. Privoxy will be installed in the folder /Library/Privoxy. It will
+start automatically whenever you start up. To prevent it from starting
+automatically, remove or rename the folder /Library/StartupItems/Privoxy.
-To run Privoxy by hand, double-click on RunPrivoxy.command. To run Privoxy from
-Terminal, execute /Library/Privoxy/RunPrivoxy.command.
+To start Privoxy by hand, double-click on StartPrivoxy.command in the /Library/
+Privoxy folder. Or, type this command in the Terminal:
+
+ /Library/Privoxy/StartPrivoxy.command
+
+
+You will be prompted for the administrator password.
-------------------------------------------------------------------------------
2.1.7. AmigaOS
latest version.
Configuration files are in /etc/privoxy, the documentation is in /usr/share/doc
-/privoxy-2.9.18 and the Log directory is in /var/log/privoxy.
+/privoxy-2.9.20 and the Log directory is in /var/log/privoxy.
-------------------------------------------------------------------------------
2.2. Building from Source
When building from a source tarball (either release version or nightly CVS
tarball), first unpack the source:
- tar xzvf privoxy-2.9.18-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.18-beta
+ tar xzvf privoxy-2.9.20-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.20-beta
For retrieving the current CVS sources, you'll need CVS installed. Note that
sources from CVS are development quality, and may not be stable, or well
5.7. Mac OSX
During installation, Privoxy is configured to start automatically when the
-system restarts. To run Privoxy by hand, double-click on the RunPrivoxy.command
-icon in the /Library/Privoxy folder. Or, type this command in the Terminal:
+system restarts. To start Privoxy by hand, double-click on the
+StartPrivoxy.command icon in the /Library/Privoxy folder. Or, type this command
+in the Terminal:
- /Library/Privoxy/RunPrivoxy.command
+ /Library/Privoxy/StartPrivoxy.command
-If you are not logged in as an administrator, you will be asked for the
-administrator password when starting Privoxy by hand.
+You will be prompted for the administrator password.
-------------------------------------------------------------------------------
5.8. AmigaOS
Unix, in local filesystem:
- user-manual file:///usr/share/doc/privoxy-2.9.18/user-manual/
+ user-manual file:///usr/share/doc/privoxy-2.9.20/user-manual/
Any platform, on local webserver (called "local-webserver"):
><TD
><PRE
CLASS="PROGRAMLISTING"
->const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $";
+>const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $";
/*********************************************************************
*
* File : $Source$
CLASS="PROGRAMLISTING"
>#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $"
/*********************************************************************
*
* File : $Source$
><H2
CLASS="SECT2"
><A
-NAME="AEN1131"
+NAME="AEN1149"
>9.1. License</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN1147"
+NAME="AEN1165"
>9.2. History</A
></H2
><P
with the team's general consensus on what should be done (see below).
</P
></LI
+><LI
+><P
+> Don't commit into the stable branch, unless immediately before a new
+ release. (See <A
+HREF="newrelease.html#VERSIONNUMBERS"
+>Version Numbers</A
+> below
+ for details.) Collect your changes on the <A
+HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
+TARGET="_top"
+>patches
+ tracker</A
+> instead.
+ </P
+></LI
></UL
>
</P
<I
CLASS="CITETITLE"
>privoxy.1</I
-> (man page) files are also now maintained
- as Docbook SGML. The finished files are all in the top-level source
- directory are generated files! Also, <TT
-CLASS="FILENAME"
->index.html</TT
->, the
- <SPAN
+> (man page), and
+ <I
+CLASS="CITETITLE"
+>config</I
+> files are also now maintained as Docbook
+ SGML. These files, when built, in the top-level source directory are
+ generated files! Also, the <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> home page, is maintained as SGML.
+> <TT
+CLASS="FILENAME"
+>index.html</TT
+> (and a
+ variation on this file, <TT
+CLASS="FILENAME"
+>privoxy-index.html</TT
+>,
+ meant for inclusion with doc packages), are maintained as SGML as well.
<I
CLASS="EMPHASIS"
>DO NOT edit these directly</I
Hal).
</P
><P
+> <TT
+CLASS="FILENAME"
+>config</TT
+> requires some special handling. The reason it
+ is maintained this way is so that the extensive comments in the file
+ mirror those in <I
+CLASS="CITETITLE"
+>user-manual</I
+>. But the conversion
+ process requires going from SGML to HTML to text to special formatting
+ required for the embedded comments. Some of this does not survive so
+ well. Especially some of the examples that are longer than 80 characters.
+ The build process for this file outputs to <TT
+CLASS="FILENAME"
+>config.new</TT
+>,
+ which should be reviewed for errors and mis-formatting. Once satisfied
+ that it is correct, then it should be hand copied to
+ <TT
+CLASS="FILENAME"
+>config</TT
+>.
+
+ </P
+><P
> Other, less formal documents (e.g. <TT
CLASS="FILENAME"
>LICENSE</TT
><H2
CLASS="SECT2"
><A
-NAME="AEN210"
+NAME="AEN221"
>3.3. Privoxy Custom Entities</A
></H2
><P
>
version string, e.g. <SPAN
CLASS="QUOTE"
->"2.9.18"</SPAN
+>"2.9.20"</SPAN
>.
</TD
></TR
<BR></P
><P
CLASS="PUBDATE"
->$Id: developer-manual.sgml,v 1.46.2.4 2002/05/29 00:30:59 mal0rd Exp $<BR></P
+>$Id: developer-manual.sgml,v 1.46.2.6 2002/08/10 11:40:25 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
> development. It is mandatory (and helpful!) reading
for anyone who wants to join the team.</P
><P
-> You can find the latest version of the this manual at <A
+> Please note that this document is constantly evolving. This copy represents
+ the state at the release of version 2.9.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
></DT
><DT
>3.3. <A
-HREF="documentation.html#AEN210"
+HREF="documentation.html#AEN221"
>Privoxy Custom Entities</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="copyright.html#AEN1131"
+HREF="copyright.html#AEN1149"
>License</A
></DT
><DT
>9.2. <A
-HREF="copyright.html#AEN1147"
+HREF="copyright.html#AEN1165"
>History</A
></DT
></DL
branches!) in <TT
CLASS="FILENAME"
>configure.in</TT
->.
+>. (RPM spec files
+ will need to be incremented as well.)
</P
></LI
><LI
></LI
><LI
><P
-> If the HTML documentation is not in sync with the SGML sources
- you need to regenerate and upload it to the webserver. (If in
- doubt, just do it.) See the Section "Updating the webserver" in
- this manual for details.
+> All documentation should be rebuild after the version bump.
+ Finished docs should be then be committed to CVS (for those
+ without the ability to build these). Some docs may require
+ rather obscure processing tools. <TT
+CLASS="FILENAME"
+>config</TT
+>,
+ the man page (and the html version of the man page), and the PDF docs
+ fall in this category. REAMDE, the man page, AUTHORS, and config
+ should all also be committed to CVS for other packageers. The
+ formal docs should be uploaded to the webserver. See the
+ Section "Updating the webserver" in this manual for details.
+ </P
+></LI
+><LI
+><P
+> All developers should look at the <TT
+CLASS="FILENAME"
+>ChangeLog</TT
+> and
+ make sure noteworthy changes are referenced.
</P
></LI
><LI
<I
CLASS="EMPHASIS"
>you must make sure that you build from clean sources by exporting
- the right version from CVS into an empty directory:</I
->.
+ the right version from CVS into an empty directory</I
+> (just press return when
+ asked for a password):
</P
><P
> <TABLE
maintainers to do this if you can't).
</P
></LI
+><LI
+><P
+> Packagers should do a <SPAN
+CLASS="QUOTE"
+>"clean"</SPAN
+> install of their
+ package after building it. So any previous installs should be
+ removed first to ensure the integrity of the newly built package.
+ Then run the package for a while to make sure there are no
+ obvious problems, before uploading.
+ </P
+></LI
></UL
>
</P
><TD
><PRE
CLASS="PROGRAMLISTING"
-> debchange -v 2.9.18-beta-1 "New upstream version"</PRE
+> debchange -v 2.9.20-beta-1 "New upstream version"</PRE
></TD
></TR
></TABLE
> This will create
<TT
CLASS="FILENAME"
->../privoxy_2.9.18-beta-1_i386.deb</TT
+>../privoxy_2.9.20-beta-1_i386.deb</TT
>
which can be uploaded. To upload the package to Sourceforge, simply
issue
>$VERSION ($CODE_STATUS)</TT
>, e.g. <I
CLASS="EMPHASIS"
->2.9.18
+>2.9.20
(beta)</I
>.
</P
>Configuration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="misc.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONFIGURATION">3. Configuration</H1
+NAME="CONFIGURATION"
+>3. Configuration</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="GETUPDATES">3.1. Where can I get updated Actions Files?</H3
+NAME="GETUPDATES"
+>3.1. Where can I get updated Actions Files?</A
+></H3
><P
> Based on your feedback and the continuing development, updated actions files will be
made available on the <A
><H3
CLASS="SECT2"
><A
-NAME="NEWCONFIG">3.2. Can I use my old config files?</H3
+NAME="NEWCONFIG"
+>3.2. Can I use my old config files?</A
+></H3
><P
> The syntax, number, and purpose of configuration files has substantially
changed from <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN266">3.3. What is an <SPAN
+NAME="AEN266"
+>3.3. What is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
-> file?</H3
+> file?</A
+></H3
><P
> <A
HREF="../user-manual/actions-file.html"
><H3
CLASS="SECT2"
><A
-NAME="ACTIONSS">3.4. The <SPAN
+NAME="ACTIONSS"
+>3.4. The <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> concept confuses me. Please list
some of these <SPAN
CLASS="QUOTE"
>"actions"</SPAN
->.</H3
+>.</A
+></H3
><P
> For a comprehensive discussion of the actions concept, please refer
to the <A
><H3
CLASS="SECT2"
><A
-NAME="AEN285">3.5. How are actions files configured? What is the easiest
-way to do this?</H3
+NAME="AEN285"
+>3.5. 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 edited
with a text editor. The probably easiest way is to access
><H3
CLASS="SECT2"
><A
-NAME="AEN293">3.6. There are several different <SPAN
+NAME="AEN293"
+>3.6. There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> files. What are
-the differences?</H3
+the differences?</A
+></H3
><P
> As of <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="YAHOO">3.7. How can I make my Yahoo/Hotmail/GMX account work?</H3
+NAME="YAHOO"
+>3.7. How can I make my Yahoo/Hotmail/GMX account work?</A
+></H3
><P
> The default configuration shouldn't impact the usability of any of these services.
It will, however, make all cookies temporary, so that your browser will forget your
><H3
CLASS="SECT2"
><A
-NAME="CONFIGFILES">3.8. What's the difference between the
+NAME="CONFIGFILES"
+>3.8. What's the difference between the
<SPAN
CLASS="QUOTE"
>"Cautious"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Advanced"</SPAN
-> defaults?</H3
+> defaults?</A
+></H3
><P
> Configuring <SPAN
CLASS="APPLICATION"
><DIV
CLASS="TABLE"
><A
-NAME="AEN328"><P
+NAME="AEN328"
+></A
+><P
><B
>Table 1. Default Configurations</B
></P
><H3
CLASS="SECT2"
><A
-NAME="BROWSECONFIG">3.9. Why can I change the configuration
-with a browser? Does that not raise security issues?</H3
+NAME="BROWSECONFIG"
+>3.9. Why can I change the configuration
+with a browser? Does that not raise security issues?</A
+></H3
><P
> It may seem strange that regular users can edit the config files with their
browsers, although the whole <TT
><H3
CLASS="SECT2"
><A
-NAME="AEN431">3.10. What is the <TT
+NAME="AEN431"
+>3.10. What is the <TT
CLASS="FILENAME"
>default.filter</TT
> file? What is a <SPAN
CLASS="QUOTE"
>"filter"</SPAN
->?</H3
+>?</A
+></H3
><P
> The <A
HREF="../user-manual/filter-file.html"
>default.filter</TT
></A
>
- file is where <SPAN
-CLASS="emphasis"
-><I
+ file is where <I
CLASS="EMPHASIS"
>filters</I
-></SPAN
> are defined, which can be used to modify or
- remove, web page content on the fly. Filters apply to <SPAN
-CLASS="emphasis"
-><I
+ remove, web page content on the fly. Filters apply to <I
CLASS="EMPHASIS"
>anything</I
-></SPAN
>
in the page source, including HTML tags, and JavaScript. Regular expressions are used
to accomplish this. There are a number of pre-defined filters to deal with common
><H3
CLASS="SECT2"
><A
-NAME="AEN447">3.11. How can I set up <SPAN
+NAME="AEN447"
+>3.11. How can I set up <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> to act as a proxy for my
- LAN?</H3
+ LAN?</A
+></H3
><P
> By default, <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN465">3.12. Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</H3
+NAME="AEN465"
+>3.12. Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</A
+></H3
><P
> The replacement for blocked images can be controlled with the <A
HREF="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"
>handle-as-image</A
></TT
>
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>and</I
-></SPAN
> <TT
CLASS="LITERAL"
><A
><H3
CLASS="SECT2"
><A
-NAME="AEN482">3.13. Why would anybody want to see a checkerboard pattern?</H3
+NAME="AEN482"
+>3.13. Why would anybody want to see a checkerboard pattern?</A
+></H3
><P
> Remember that <A
HREF="general.html#WHATSANAD"
decent, but it shows you that and where images were blocked, which can be very
helpful in case some navigation aid or otherwise innocent image was
erraneously blocked. Some people might also enjoy seeing how many banners
- they <SPAN
-CLASS="emphasis"
-><I
+ they <I
CLASS="EMPHASIS"
>don't</I
-></SPAN
> have to see..</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN487">3.14. I see some images being replaced by a text
-instead of the checkerboard image. Why and how do I get rid of this?</H3
+NAME="AEN487"
+>3.14. I see some images being replaced by a text
+instead of the checkerboard image. Why and how do I get rid of this?</A
+></H3
><P
> This happens when the banners are not embedded in the HTML code of the
page itself, but in separate HTML (sub)documents that are loaded into (i)frames
><H3
CLASS="SECT2"
><A
-NAME="SRVANY">3.15. Can <SPAN
+NAME="SRVANY"
+>3.15. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a service
-on Win2K/NT?</H3
+on Win2K/NT?</A
+></H3
><P
> Yes, it can run as a system service using <B
CLASS="COMMAND"
><H3
CLASS="SECT2"
><A
-NAME="OTHERPROXY">3.16. How can I make <SPAN
+NAME="OTHERPROXY"
+>3.16. How can I make <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> work with other
proxies like <SPAN
CLASS="APPLICATION"
>Squid</SPAN
->?</H3
+>?</A
+></H3
><P
> This can be done and is often useful to combine the benefits of
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="TRANSPARENT">3.17. Can <SPAN
+NAME="TRANSPARENT"
+>3.17. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a <SPAN
CLASS="QUOTE"
>"transparent"</SPAN
-> proxy?</H3
+> proxy?</A
+></H3
><P
> No, <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="misc.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Contacting the developers, Bug Reporting and Feature Requests</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="trouble.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONTACT">6. Contacting the developers, Bug Reporting and Feature Requests</H1
+NAME="CONTACT"
+>6. Contacting the developers, Bug Reporting and Feature Requests</A
+></H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT">6.1. Get Support</H2
+NAME="CONTACT-SUPPORT"
+>6.1. Get Support</A
+></H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS">6.2. Report Bugs</H2
+NAME="CONTACT-BUGS"
+>6.2. Report Bugs</A
+></H2
><P
-> Please report all bugs <SPAN
-CLASS="emphasis"
-><I
+> Please report all bugs <I
CLASS="EMPHASIS"
>only</I
-></SPAN
> through our
bug tracker:
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE">6.3. Request New Features</H2
+NAME="CONTACT-FEATURE"
+>6.3. Request New Features</A
+></H2
><P
> You are welcome to submit ideas on new features or other proposals
for improvement through our feature request tracker at
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-ADS">6.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS"
+>6.4. Report Ads or Other Actions-Related Problems</A
+></H2
><P
> Please send feedback on ads that slipped through, innocent images that were blocked,
and any other problems relating to the <TT
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-OTHER">6.5. Other</H2
+NAME="CONTACT-OTHER"
+>6.5. Other</A
+></H2
><P
>For any other issues, feel free to use the mailing lists. Technically interested users
and people who wish to contribute to the project are also welcome on the developers list!
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="trouble.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Copyright, License and History</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT">7. Privoxy Copyright, License and History</H1
+NAME="COPYRIGHT"
+>7. Privoxy Copyright, License and History</A
+></H1
><P
> Copyright © 2001, 2002 by Privoxy Developers <TT
CLASS="EMAIL"
><H2
CLASS="SECT2"
><A
-NAME="AEN841">7.1. License</H2
+NAME="AEN841"
+>7.1. License</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN857">7.2. History</H2
+NAME="AEN857"
+>7.2. History</A
+></H2
><P
> In the beginning, there was the
<A
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
>General Information</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="GENERAL">1. General Information</H1
+NAME="GENERAL"
+>1. General Information</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="NEWJB">1.1. What is this new version of <SPAN
+NAME="NEWJB"
+>1.1. What is this new version of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> In the beginning, there was the
<A
><H3
CLASS="SECT2"
><A
-NAME="AEN45">1.2. Why <SPAN
+NAME="AEN45"
+>1.2. Why <SPAN
CLASS="QUOTE"
>"Privoxy"</SPAN
->? Why a name change at all?</H3
+>? Why a name change at all?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
> is the
<SPAN
CLASS="QUOTE"
->"<SPAN
-CLASS="emphasis"
-><I
+>"<I
CLASS="EMPHASIS"
>Privacy Enhancing Proxy</I
-></SPAN
>"</SPAN
>. Also, its content
modification and junk suppression allow you to browse your
<SPAN
CLASS="QUOTE"
->"<SPAN
-CLASS="emphasis"
-><I
+>"<I
CLASS="EMPHASIS"
>private</I
-></SPAN
> edition"</SPAN
> of the web.</P
><P
><H3
CLASS="SECT2"
><A
-NAME="DIFFERS">1.3. How does <SPAN
+NAME="DIFFERS"
+>1.3. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> differ
from the old <SPAN
CLASS="APPLICATION"
>Junkbuster?</SPAN
+></A
></H3
><P
> <SPAN
><H3
CLASS="SECT2"
><A
-NAME="PROXYMORON">1.4. What is a <SPAN
+NAME="PROXYMORON"
+>1.4. What is a <SPAN
CLASS="QUOTE"
>"proxy"</SPAN
>? How does
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> work?</H3
+> work?</A
+></H3
><P
> A web proxy is a service, based on a software such as <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="WHATSANAD">1.5. How does <SPAN
+NAME="WHATSANAD"
+>1.5. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> know what is
-an ad, and what is not?</H3
+an ad, and what is not?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>'s approach to blocking ads is twofold:</P
><P
-> First, there are certain patterns in the <SPAN
-CLASS="emphasis"
-><I
+> First, there are certain patterns in the <I
CLASS="EMPHASIS"
>locations</I
-></SPAN
> (URLs)
of banner images. This applies to both the path (you wouldn't guess how many
web sites serve their banners from a directory called <SPAN
patterns</A
> to sort out and block the requests for banners.</P
><P
-> Second, banners tend to come in certain <SPAN
-CLASS="emphasis"
-><I
+> Second, banners tend to come in certain <I
CLASS="EMPHASIS"
>sizes</I
-></SPAN
>. But you
can't tell the size of an image by its URL without downloading it, and if you
do, it's too late to save bandwidth. Therefore, <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN136">1.6. Can <SPAN
+NAME="AEN136"
+>1.6. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> make mistakes?
-This does not sound very scientific.</H3
+This does not sound very scientific.</A
+></H3
><P
> Actually, it's a black art ;-) And yes, it is always possible to have a broad
rule accidentally block or change something by mistake. There is a good chance
><H3
CLASS="SECT2"
><A
-NAME="BROWSERS2">1.7. My browser does the same things as
+NAME="BROWSERS2"
+>1.7. My browser does the same things as
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> at all?</H3
+> at all?</A
+></H3
><P
-> Modern browsers do indeed have <SPAN
-CLASS="emphasis"
-><I
+> Modern browsers do indeed have <I
CLASS="EMPHASIS"
>some</I
-></SPAN
> of the same
functionality as <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="LICENSE">1.8. Is there is a license or fee? What about a
-warranty? Registration?</H3
+NAME="LICENSE"
+>1.8. Is there is a license or fee? What about a
+warranty? Registration?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
that should be included.
</P
><P
-> There is <SPAN
-CLASS="emphasis"
-><I
+> There is <I
CLASS="EMPHASIS"
>no warranty</I
-></SPAN
> of any kind, expressed, implied or otherwise.
That is something that would cost real money ;-) There is no registration either.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> really is <SPAN
-CLASS="emphasis"
-><I
+> really is <I
CLASS="EMPHASIS"
>free</I
-></SPAN
>
in every respect!
</P
><H3
CLASS="SECT2"
><A
-NAME="JOINTEAM">1.9. I would like to help you, what do I do?</H3
+NAME="JOINTEAM"
+>1.9. I would like to help you, what do I do?</A
+></H3
><DIV
CLASS="SECT3"
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-MONEY">1.9.1. Money Money Money</H4
+NAME="JOINTEAM-MONEY"
+>1.9.1. Money Money Money</A
+></H4
><P
> We, of course, welcome donations and could use money for domain registering,
buying software to test <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-SOFTWARE">1.9.2. Software</H4
+NAME="JOINTEAM-SOFTWARE"
+>1.9.2. Software</A
+></H4
><P
> If you are a vendor of a web-related software like a browser, web server
or proxy, and would like us to ensure that <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-WORK">1.9.3. You want to work with us?</H4
+NAME="JOINTEAM-WORK"
+>1.9.3. You want to work with us?</A
+></H4
><P
> Well, helping the team is always a good idea. We welcome new developers,
packaging gurus or documentation writers. Simply <A
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Frequently Asked Questions</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="NEXT"
TITLE="General Information"
HREF="general.html"><LINK
><H1
CLASS="TITLE"
><A
-NAME="AEN2">Privoxy Frequently Asked Questions</H1
+NAME="AEN2"
+>Privoxy Frequently Asked Questions</A
+></H1
><P
CLASS="PUBDATE"
> <SUB
><BR></P
><P
CLASS="PUBDATE"
->$Id: faq.sgml,v 1.61.2.13 2002/08/06 11:55:32 oes Exp $<BR></P
+>$Id: faq.sgml,v 1.61.2.15 2002/08/10 11:34:22 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"><P
+NAME="AEN9"
+></A
+><P
></P
><P
> This FAQ gives quick answers to frequently asked questions about
HREF="http://www.privoxy.org/"
TARGET="_top"
>Privoxy</A
->
- . It can't and doesn't replace the
+>.
+ It can't and doesn't replace the
<A
HREF="../user-manual/index.html"
TARGET="_top"
Junkbuster</SPAN
> (tm).</P
><P
-> You can find the latest version of the document at <A
+> Please note that this document is constantly evolving. This copy represents
+ the state at the release of version 2.9.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
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="general.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Installation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="general.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION">2. Installation</H1
+NAME="INSTALLATION"
+>2. Installation</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="WHICHBROWSERS">2.1. Which browsers are supported by <SPAN
+NAME="WHICHBROWSERS"
+>2.1. Which browsers are supported by <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> Any browser that can be configured to use a proxy, which
should be virtually all browsers. Direct browser support is not necessary
><H3
CLASS="SECT2"
><A
-NAME="WHICHOS">2.2. Which operating systems are supported?</H3
+NAME="WHICHOS"
+>2.2. Which operating systems are supported?</A
+></H3
><P
> At present, <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="NEWINSTALL">2.3. Can I install
+NAME="NEWINSTALL"
+>2.3. Can I install
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> over <SPAN
CLASS="APPLICATION"
>Junkbuster</SPAN
->?</H3
+>?</A
+></H3
><P
> We recommend you un-install <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN209">2.4. I just installed <SPAN
+NAME="AEN209"
+>2.4. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>. Is there anything
-special I have to do now?</H3
+special I have to do now?</A
+></H3
><P
> All browsers must be told to use <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="LOCALHOST">2.5. What is the proxy address of <SPAN
+NAME="LOCALHOST"
+>2.5. What is the proxy address of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> If you set up the <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="NOTHING">2.6. I just installed <SPAN
+NAME="NOTHING"
+>2.6. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, and nothing is happening.
-All the ads are there. What's wrong?</H3
+All the ads are there. What's wrong?</A
+></H3
><P
> Did you configure your browser to use <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="general.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Miscellaneous</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="trouble.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="MISC">4. Miscellaneous</H1
+NAME="MISC"
+>4. Miscellaneous</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN523">4.1. How much does <SPAN
+NAME="AEN523"
+>4.1. How much does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> slow my browsing down? This
-has to add extra time to browsing.</H3
+has to add extra time to browsing.</A
+></H3
><P
> It should not slow you down any in real terms, and may actually help
speed things up since ads, banners and other junk are not being displayed.
><H3
CLASS="SECT2"
><A
-NAME="LOADINGTIMES">4.2. I noticed considerable
-delays in page requests compared to the old Junkbuster. What's wrong?</H3
+NAME="LOADINGTIMES"
+>4.2. I noticed considerable
+delays in page requests compared to the old Junkbuster. What's wrong?</A
+></H3
><P
> If you use any <TT
CLASS="LITERAL"
><H3
CLASS="SECT2"
><A
-NAME="CONFIGURL">4.3. What are "http://config.privoxy.org/" and
-"http://p.p/"?</H3
+NAME="CONFIGURL"
+>4.3. What are "http://config.privoxy.org/" and
+"http://p.p/"?</A
+></H3
><P
> <A
HREF="http://config.privoxy.org/"
CLASS="APPLICATION"
>Privoxy</SPAN
> for the request,
- hence it could not be intercepted, and you have accessed the <SPAN
-CLASS="emphasis"
-><I
+ hence it could not be intercepted, and you have accessed the <I
CLASS="EMPHASIS"
>real</I
-></SPAN
>
web site at config.privoxy.org.</P
><P
>Privoxy</SPAN
>, http://example.com/show-proxy-args and http://i.j.b/,
are no longer supported. If you still use such an old version, you should really consider
- upgrading to 2.9.18.</P
+ upgrading to 2.9.20.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="BLOCKLIST">4.4. Do you still maintain the blocklists?</H3
+NAME="BLOCKLIST"
+>4.4. Do you still maintain the blocklists?</A
+></H3
><P
> No. The patterns for blocking now reside (among other things) in the <A
HREF="../user-manual/actions-file.html"
><H3
CLASS="SECT2"
><A
-NAME="NEWADS">4.5. How can I submit new ads?</H3
+NAME="NEWADS"
+>4.5. How can I submit new ads?</A
+></H3
><P
>Yes, absolutely! Please see the <A
HREF="contact.html"
><H3
CLASS="SECT2"
><A
-NAME="IP">4.6. How can I hide my IP address?</H3
+NAME="IP"
+>4.6. How can I hide my IP address?</A
+></H3
><P
> If you run both the browser and the proxy locally, you cannot hide your IP
address with <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN583">4.7. Can <SPAN
+NAME="AEN583"
+>4.7. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> guarantee I am anonymous?</H3
+> guarantee I am anonymous?</A
+></H3
><P
> No. Your chances of remaining anonymous are greatly improved, but unless you
are an expert on Internet security it would be safest to assume that
CLASS="APPLICATION"
>Privoxy</SPAN
> can remove various information about you,
- and allows <SPAN
-CLASS="emphasis"
-><I
+ and allows <I
CLASS="EMPHASIS"
>you</I
-></SPAN
> more freedom to decide which sites
you can trust, and what details you want to reveal. But it's still possible
that web sites can find out who you are. Here's one way this can happen.</P
><H3
CLASS="SECT2"
><A
-NAME="AEN594">4.8. Might some things break because header information or
-content is being altered?</H3
+NAME="AEN594"
+>4.8. Might some things break because header information or
+content is being altered?</A
+></H3
><P
> Definitely. More and more sites use HTTP header content to decide what to
display and how to display it. There is many ways that this can be handled,
><H3
CLASS="SECT2"
><A
-NAME="AEN605">4.9. Can <SPAN
+NAME="AEN605"
+>4.9. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> act as a <SPAN
CLASS="QUOTE"
>"caching"</SPAN
> proxy to
-speed up web browsing?</H3
+speed up web browsing?</A
+></H3
><P
> No, it does not have this ability at all. You want something like
<A
><H3
CLASS="SECT2"
><A
-NAME="AEN615">4.10. What about as a firewall? Can <SPAN
+NAME="AEN615"
+>4.10. What about as a firewall? Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> protect me?</H3
+> protect me?</A
+></H3
><P
> Not in the way you mean, or in the way a true firewall can.
<SPAN
>Privoxy</SPAN
> can help protect your privacy, but not
protect you from intrusion attempts. It is, of course, perfectly possible
- and recommended to use <SPAN
-CLASS="emphasis"
-><I
+ and recommended to use <I
CLASS="EMPHASIS"
>both</I
-></SPAN
>.</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN621">4.11. I have large empty spaces / a checkerboard pattern now where
-ads used to be. Why?</H3
+NAME="AEN621"
+>4.11. I have large empty spaces / a checkerboard pattern now where
+ads used to be. Why?</A
+></H3
><P
> It would be technically possible eliminate the banners in a way that frees
their screen estate in many cases, by doing all banner blocking with filters,
><H3
CLASS="SECT2"
><A
-NAME="AEN626">4.12. How can <SPAN
+NAME="AEN626"
+>4.12. How can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> filter Secure (HTTPS) URLs?</H3
+> filter Secure (HTTPS) URLs?</A
+></H3
><P
> Since secure HTTP connections are encrypted SSL sessions between your browser
- and the secure site, and are meant to be reliably <SPAN
-CLASS="emphasis"
-><I
+ and the secure site, and are meant to be reliably <I
CLASS="EMPHASIS"
>secure</I
-></SPAN
>,
there is little that <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN637">4.13. <SPAN
+NAME="AEN637"
+>4.13. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> runs as a <SPAN
CLASS="QUOTE"
>"server"</SPAN
>. How
-secure is it? Do I need to take any special precautions?</H3
+secure is it? Do I need to take any special precautions?</A
+></H3
><P
> There are no known exploits that might affect
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="TURNOFF">4.14. How can I temporarily disable <SPAN
+NAME="TURNOFF"
+>4.14. How can I temporarily disable <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> The easiest way is to access <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="REALLYOFF">4.15. When <SPAN
+NAME="REALLYOFF"
+>4.15. When <SPAN
CLASS="QUOTE"
>"disabled"</SPAN
> is <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> totally
-out of the picture?</H3
+out of the picture?</A
+></H3
><P
> No, this just means all filtering and actions are disabled.
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="SEEALSO">4.16. Where can I find more information about <SPAN
+NAME="SEEALSO"
+>4.16. Where can I find more information about <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
-and related issues?</H3
+and related issues?</A
+></H3
><P
> Other references and sites of interest to <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="trouble.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="misc.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="TROUBLE">5. Troubleshooting</H1
+NAME="TROUBLE"
+>5. Troubleshooting</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN718">5.1. I just upgraded and am getting <SPAN
+NAME="AEN718"
+>5.1. I just upgraded and am getting <SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
>
-with every web page?</H3
+with every web page?</A
+></H3
><P
> Either <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN731">5.2. I just added a new rule, but the steenkin ad is
-still getting through. How?</H3
+NAME="AEN731"
+>5.2. 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 probably be
held in the browser's cache for some time, so it will be displayed without
><H3
CLASS="SECT2"
><A
-NAME="BADSITE">5.3. One of my favorite sites does not work with <SPAN
+NAME="BADSITE"
+>5.3. One of my favorite sites does not work with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>.
-What can I do?</H3
+What can I do?</A
+></H3
><P
> First verify that it is indeed a <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="DUN">5.4. After installing <SPAN
+NAME="DUN"
+>5.4. After installing <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, I have to log in
-every time I start IE. What gives?</H3
+every time I start IE. What gives?</A
+></H3
><P
> This is a quirk that effects the installation of
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="FTP">5.5. I cannot connect to any FTP sites. <SPAN
+NAME="FTP"
+>5.5. I cannot connect to any FTP sites. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
- seems to be blocking me.</H3
+ seems to be blocking me.</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="OSXIE">5.6. In Mac OSX, I can't configure Microsoft Internet Explorer to use
+NAME="OSXIE"
+>5.6. In Mac OSX, I can't configure Microsoft Internet Explorer to use
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> as the HTTP proxy.</H3
+> as the HTTP proxy.</A
+></H3
><P
> Microsoft Internet Explorer (in versions like 5.1) respects system-wide
network settings. In order to change the HTTP proxy, open System
><H3
CLASS="SECT2"
><A
-NAME="OSXUNINSTALL">5.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
+NAME="OSXUNINSTALL"
+>5.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
uninstall it. Now the finder tells me I don't have sufficient privileges to
- empty the trash.</H3
+ empty the trash.</A
+></H3
><P
> Just dragging the <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="misc.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy - Home Page</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><META
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><META
NAME="KEYWORD"
CONTENT="privoxy"><META
NAME="KEYWORD"
><H1
CLASS="TITLE"
><A
-NAME="AEN2">Privoxy - Home Page</H1
+NAME="AEN2"
+>Privoxy - Home Page</A
+></H1
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN28"><P
+NAME="AEN28"
+></A
+><P
></P
><P
>
Junkbuster</SPAN
> (tm).</P
><P
-> The most recent release is 2.9.18 (beta).
+> The most recent release is 2.9.20 (beta).
</P
><P
></P
><HR></DIV
><DIV
CLASS="SECT1"
-><H3
+><H2
CLASS="SECT1"
><A
-NAME="DOWNLOAD">Download</H3
+NAME="DOWNLOAD"
+>Download</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H3
+><HR><H2
CLASS="SECT1"
><A
-NAME="DOCS">Documentation</H3
+NAME="DOCS"
+>Documentation</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H3
+><HR><H2
CLASS="SECT1"
><A
-NAME="MOREINFO">More information</H3
+NAME="MOREINFO"
+>More information</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H2
+><HR><H1
CLASS="SECT1"
><A
-NAME="AEN91"></H2
+NAME="AEN91"
+></A
+></H1
><P
><DIV
CLASS="INFORMALTABLE"
><A
-NAME="AEN94"><P
+NAME="AEN94"
+></A
+><P
></P
><TABLE
BORDER="0"
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Main Configuration File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN1637"
+NAME="AEN1640"
>8.1. Finding the Right Mix</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN1644"
+NAME="AEN1647"
>8.2. How to Edit</A
></H2
><P
>{
+<A
HREF="actions-file.html#HANDLE-AS-IMAGE"
-TARGET="_top"
>handle-as-image</A
> }</TT
>,
>{
+<A
HREF="actions-file.html#BLOCK"
-TARGET="_top"
>block</A
> }</TT
>, resulting
><H3
CLASS="SECT3"
><A
-NAME="AEN1708"
+NAME="AEN1711"
>8.4.1. The Domain Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN1770"
+NAME="AEN1773"
>8.4.2. The Path Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2698"
+NAME="AEN2701"
>8.5.21. Summary</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2750"
+NAME="AEN2753"
>8.7.1. default.action</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2907"
+NAME="AEN2910"
>8.7.2. user.action</A
></H3
><P
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="See Also"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN3462"
+NAME="AEN3465"
>14.2. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
Privoxy main page:
</P
><A
-NAME="AEN3477"
+NAME="AEN3480"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN3485"
+NAME="AEN3488"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN3490"
+NAME="AEN3493"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN3495"
+NAME="AEN3498"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN3500"
+NAME="AEN3503"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN3506"
+NAME="AEN3509"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN3510"
+NAME="AEN3513"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN3513"
+NAME="AEN3516"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Credit: The site which gave us the general idea for these bookmarklets is
<A
-HREF="http://www.bookmarklets.com"
+HREF="http://www.bookmarklets.com/"
TARGET="_top"
>www.bookmarklets.com</A
>. They
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><TD
><PRE
CLASS="SCREEN"
->user-manual file:///usr/share/doc/privoxy-2.9.18/user-manual/</PRE
+>user-manual file:///usr/share/doc/privoxy-2.9.20/user-manual/</PRE
></TD
></TR
></TABLE
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN576"
+NAME="AEN579"
>6.1. Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Templates"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Contacting the Developers, Bug Reporting and Feature
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN3212"
+NAME="AEN3215"
>12.1. License</A
></H2
><P
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN3010"
+NAME="AEN3013"
>9.1. Filter File Tutorial</A
></H2
><P
<HTML
><HEAD
><TITLE
->Privoxy 2.9.18 User Manual</TITLE
+>Privoxy 2.9.20 User Manual</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
CLASS="TITLE"
><A
NAME="AEN2"
->Privoxy 2.9.18 User Manual</A
+>Privoxy 2.9.20 User Manual</A
></H1
><P
CLASS="PUBDATE"
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 1.123.2.14 2002/08/06 09:16:13 oes Exp $<BR></P
+>$Id: user-manual.sgml,v 1.123.2.16 2002/08/09 19:20:54 david__schmidt Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
>.
Please see the <A
HREF="contact.html"
-TARGET="_top"
>Contact section</A
> on how to
contact the developers.
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN576"
+HREF="configuration.html#AEN579"
>Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN1637"
+HREF="actions-file.html#AEN1640"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN1644"
+HREF="actions-file.html#AEN1647"
>How to Edit</A
></DT
><DT
><DL
><DT
>22<A
-HREF="actions-file.html#AEN1675"
+HREF="actions-file.html#AEN1678"
></A
></DT
><DT
>8.4.1. <A
-HREF="actions-file.html#AEN1708"
+HREF="actions-file.html#AEN1711"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN1770"
+HREF="actions-file.html#AEN1773"
>The Path Pattern</A
></DT
></DL
></DT
><DT
>8.5.21. <A
-HREF="actions-file.html#AEN2698"
+HREF="actions-file.html#AEN2701"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN2750"
+HREF="actions-file.html#AEN2753"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN2907"
+HREF="actions-file.html#AEN2910"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN3010"
+HREF="filter-file.html#AEN3013"
>Filter File Tutorial</A
></DT
></DL
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN3212"
+HREF="copyright.html#AEN3215"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN3462"
+HREF="appendix.html#AEN3465"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-2.9.18-1.rpm</TT
+>rpm -Uvh privoxy-2.9.20-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-2.9.18-1.src.rpm</TT
+>rpm --rebuild privoxy-2.9.20-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
> DEBs can be installed with <TT
CLASS="LITERAL"
>dpkg -i
- privoxy_2.9.18-1.deb</TT
+ privoxy_2.9.20-1.deb</TT
>, and will use
<TT
CLASS="FILENAME"
>2.1.6. Mac OSX</A
></H3
><P
-> Unzip the downloaded package (you can either double-click on the file
- in the finder, or on the desktop if you downloaded it there). The
- Privoxy.pkg package should appear after unzipping. Then,
- double-click on that Privoxy.pkg package installer icon and follow
- the installation process.
+> Unzip the downloaded file (you can either double-click on the file
+ from the finder, or from the desktop if you downloaded it there).
+ Then, double-click on the package installer icon named
+ <TT
+CLASS="LITERAL"
+>Privoxy.pkg</TT
+>
+ and follow the installation process.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
CLASS="LITERAL"
>/Library/Privoxy</TT
>.
- It will run automatically whenever you start up. To prevent it from
- running automatically, remove or rename the folder
+ It will start automatically whenever you start up. To prevent it from
+ starting automatically, remove or rename the folder
<TT
CLASS="LITERAL"
>/Library/StartupItems/Privoxy</TT
>. </P
><P
-> To run Privoxy by hand, double-click on
+> To start Privoxy by hand, double-click on
<TT
CLASS="LITERAL"
->RunPrivoxy.command</TT
->.
- To run Privoxy from Terminal, execute
+>StartPrivoxy.command</TT
+> in the
<TT
CLASS="LITERAL"
->/Library/Privoxy/RunPrivoxy.command</TT
->. </P
+>/Library/Privoxy</TT
+> folder.
+ Or, type this command in the Terminal:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> /Library/Privoxy/StartPrivoxy.command
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> You will be prompted for the administrator password.</P
></DIV
><DIV
CLASS="SECT3"
>, the
documentation is in <TT
CLASS="FILENAME"
->/usr/share/doc/privoxy-2.9.18</TT
+>/usr/share/doc/privoxy-2.9.20</TT
>
and the Log directory is in <TT
CLASS="FILENAME"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-2.9.18-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.18-beta</PRE
+> tar xzvf privoxy-2.9.20-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.20-beta</PRE
></TD
></TR
></TABLE
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.2.9.18,
+>, v.2.9.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 version 3.0 is currently nearing
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Privoxy 2.9.18 User Manual</TD
+>Privoxy 2.9.20 User Manual</TD
><TD
WIDTH="34%"
ALIGN="center"
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Note to Upgraders"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN384"
+NAME="AEN388"
></A
><P
><B
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Copyright, License and History"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN435"
+NAME="AEN439"
></A
><P
><B
CLASS="APPLICATION"
>Privoxy</SPAN
> is configured to
- start automatically when the system restarts. To run Privoxy by hand,
+ start automatically when the system restarts. To start Privoxy by hand,
double-click on the <TT
CLASS="LITERAL"
->RunPrivoxy.command</TT
+>StartPrivoxy.command</TT
> icon in the
<TT
CLASS="LITERAL"
><TD
><PRE
CLASS="SCREEN"
-> /Library/Privoxy/RunPrivoxy.command
+> /Library/Privoxy/StartPrivoxy.command
</PRE
></TD
></TR
></TABLE
></P
><P
-> If you are not logged in as an administrator, you will be asked for the
- administrator password when starting <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- by hand.</P
+> You will be prompted for the administrator password.</P
></DIV
><DIV
CLASS="SECT2"
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Filter File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy 2.9.18 User Manual"
+TITLE="Privoxy 2.9.20 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 2.9.18 User Manual</TH
+>Privoxy 2.9.20 User Manual</TH
></TR
><TR
><TD
projects / privoxy.git / commitdiff