Authors of Privoxy v2.9.x and 3.x
===========================================================================
-Current Developement Team:
+Current Project Developers:
- Andreas Oesterhelt (lead developer)
- Hal Burgiss (docs)
- David Schmidt (OS/2, Mac OSX ports)
-
+ Jon Foster
+ Andreas Oesterhelt
+ Stefan Waldherr
+ Thomas Steudten
+ Rodney Stromlund
-Current and Former Project Contributors:
+Current Project Contributors:
Johny Agotnes
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
+ Hal Burgiss (docs)
Mattes Dolak
- Jon Foster
Karsten Hopp (Red Hat)
Alexander Lazic
Daniel Leite
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
- Thomas Steudten
+ David Schmidt (OS/2, Mac OSX ports)
Joerg Strohmayer (Amiga)
- Rodney Stromlund
- Sviatoslav Sviridov
Sarantis Paskalis
- Stefan Waldherr
Based in part on code originally developed by:
*
*********************************************************************/
-This README is included with Privoxy 3.0.1. See http://www.privoxy.org/ for
-more information. The current code level is stable.
-------------------------------------------------------------------------------
+ **********************************************************
+
+ NOTE: This is a pre-release version of Privoxy from the "stable" CVS branch.
+ It is being readied for the next stable release -- 3.0.1 which could happen
+ "soon". While this tree is in a transition state, the version will be
+ intentionally stamped as "0.0.0" so as to make it clear that this code is not
+ yet ready for release. If you try this code, and find problems which seem to
+ be bugs, please report it to the developers list.
+
+ **********************************************************
+
Privoxy is a web proxy with advanced filtering capabilities for protecting
privacy, filtering web page content, managing cookies, controlling access, and
removing ads, banners, pop-ups and other obnoxious Internet junk. Privoxy has a
The actions list can be configured via the web interface accessed via http://
p.p/, as well other options.
+All configuration files are subject to unannounced changes during the
+development process.
+
-------------------------------------------------------------------------------
5. DOCUMENTATION
-There should be documentation in the 'doc' subdirectory. In particular, see the
-User Manual there, the FAQ, and those interested in Privoxy development, should
-look at developer-manual.
+There should be documentation in the 'doc' subdirectory, but it is not
+completed at this point. In particular, see the User Manual there, the FAQ, and
+those interested in Privoxy development, should look at developer-manual.
-The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter'.
+The most up to date source of information on the current development version,
+may still be either comments in the source code, or the included configuration
+files. The source and configuration files are all well commented. The main
+configuration files are: 'config', 'default.action', and 'default.filter' in
+the toplevel source directory.
Included documentation may vary according to platform and packager. All
documentation is posted on http://www.privoxy.org, in case you don't have it,
Copyright © 2001, 2002 by Privoxy Developers
-$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 Exp $
+$Id: developer-manual.sgml,v 1.46.2.8 2002/08/17 00:16:10 hal9 Exp $
The developer manual provides guidance on coding, testing, packaging,
documentation and other issues of importance to those involved with Privoxy
join the team.
Please note that this document is constantly evolving. This copy represents the
-state at the release of version 3.0.1. You can find the latest version of the
+state at the release of version 3.0.0. 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.
2. The CVS Repository
2.1. Access to CVS
- 2.2. Branches
- 2.3. CVS Commit Guidelines
+ 2.2. CVS Commit Guideline
+ 2.3. Discussing Changes First
3. Documentation Guidelines
1.1. Quickstart to Privoxy Development
-The first step is to join the developer's mailing list. You can submit your
-ideas, or even better patches. Patches are best submitted to the Sourceforge
-tracker set up for this purpose, but can be sent to the list for review too.
+You'll need an account on Sourceforge to support our development. Mail your ID
+to the list and wait until a project manager has added you.
-You will also need to have a cvs package installed, which will entail having
-ssh installed as well (which seems to be a requirement of SourceForge), in
-order to access the cvs repository. Having the GNU build tools is also going to
-be important (particularly, autoconf and gmake).
-
-For the time being (read, this section is under construction), you can also
-refer to the extensive comments in the source code. In fact, reading the code
-is recommended in any case.
+For the time being (read, this section is under construction), please refer to
+the extensive comments in the source code.
-------------------------------------------------------------------------------
2. The CVS Repository
-If you become part of the active development team, you will eventually need
-write access to our holy grail, the CVS repository. One of the team members
-will need to set this up for you. Please read this chapter completely before
-accessing via CVS.
+If you intend to help us with programming, documentation or packaging you will
+need write access to our holy grail, the CVS repository. Please read this
+chapter completely before accessing via CVS.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-2.2. Branches
-
-Within the CVS repository, there are modules and branches. As mentioned, the
-sources are in the current "module". Other modules are present for platform
-specific issues. There is a webview of the CVS hierarchy at http://
-cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/, which might help with
-visualizing how these pieces fit together.
-
-Branches are used to fork a sub-development path from the main trunk. Within
-the current module where the sources are, there is always at least one "branch"
-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 only used for
-bugfixes, which have had prior testing before being committed to CVS. (See
-Version Numbers below for details on versioning.)
-
-This will result in at least two active branches, which means there may be
-occasions that require the same (or similar) item to be checked into to two
-different places (assuming its a bugfix and needs fixing in both the stable and
-unstable trees). This also means that in order to have access to both trees,
-both will have to be checked out separately. Use the cvs -r flag to check out a
-branch, e.g: cvs co -r v_3_0_branch current.
-
--------------------------------------------------------------------------------
-
-2.3. CVS Commit Guidelines
+2.2. CVS Commit Guideline
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
+made to ensure that it is readable, compilable and consistent at all times. We
+therefore ask anyone with CVS access to strictly adhere to the following
guidelines:
-Basic Guidelines, for all branches:
-
* Never (read: never, ever) be tempted to commit that small change without
testing it thoroughly first. When we're close to a public release, ask a
fellow developer to review your changes.
necessary, prepare the commit messages in advance.
* Before changing things on CVS, make sure that your changes are in line with
- the team's general consensus on what should be done.
+ the team's general consensus on what should be done (see below).
- * Note that near a major public release, we get more cautious. There is
- always the possibility to submit a patch to the patch tracker instead.
+ * 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.
-Stable branches are handled with more care, especially after the initial *.*.0
-release, and we are just in bugfix mode. In addition to the above, the below
-applies only to the stable branch (currently the v_3_0_branch branch):
+-------------------------------------------------------------------------------
+
+2.3. Discussing Changes First
+
+We don't have a too formal policy on this, just use common sense. Hints: If it
+is..
- * Do not commit anything unless your proposed changes have been well tested
- first, preferably by other members of the project, or have prior approval
- of the project leaders or consensus of the devel list.
+ 1. ..a bug-fix / clean-up / cosmetic thing: shoot
- * Where possible, bugfixes and changes should be tested in the main
- development trunk first. There may be occasions where this is not feasible,
- though.
+ 2. ..a new feature that can be turned off: shoot
- * Alternately, proposed changes can be submitted as patches to the patch
- tracker on Sourceforge first: http://sourceforge.net/tracker/?group_id=
- 11118&atid=311118. Then ask for peer review.
+ 3. ..a clear improvement w/o side effects on other parts of the code: shoot
- * Do not even think about anything except bugfixes. No new features!
+ 4. ..a matter of taste: ask the list
+ 5. ..a major redesign of some part of the code: ask the list
+
+Note that near a major public release, we get a bit more cautious - if unsure,
+it doesn't hurt to ask first. There is always the possibility to submit a patch
+to the patches tracker instead.
+
-------------------------------------------------------------------------------
3. Documentation Guidelines
* Commonly used "internal entities":
- p-version: the Privoxy version string, e.g. "3.0.1".
+ p-version: the Privoxy version string, e.g. "3.0.0".
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").
Example for file comments:
-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 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.8 2002/08/17 00:16:10 hal9 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
Example for file header comments:
-#ifndef _FILENAME_H
-#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 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.8 2002/08/17 00:16:10 hal9 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:
6.1. Version numbers
First you need to determine which version number the release will have. Privoxy
-version numbers consist of three numbers, separated by dots, like in X.Y.Z
-(e.g. 3.0.0), where:
+version numbers consist of three numbers, separated by dots, like in X.Y.Z,
+where:
* X, the version major, is rarely ever changed. It is increased by one if
turning a development branch into stable substantially changes the
distinguished from released versions. The point version is reset to zero
when the minor changes.
- Stable branches work a little differently, since there should be little to
- no development happening in such branches. Remember, only bugfixes, which
- presumably should have had some testing before being committed. Stable
- branches will then have their version reported as 0.0.0, during that period
- between releases when changes are being added. This is to denote that this
- code is not for release. Then as the release nears, the version is bumped
- according: e.g. 3.0.1 -> 0.0.0 -> 3.0.2.
-
-In summary, the main CVS trunk is the development branch where new features are
-being worked on for the next stable series. This should almost always be where
-the most activity takes place. There is always at least one stable branch from
-the trunk, e.g now it is 3.0, which is only used to release stable versions.
-Once the initial *.0 release of the stable branch has been done, then as a
-rule, only bugfixes that have had prior testing should be committed to the
-stable branch. Once there are enough bugfixes to justify a new release, the
-version of this branch is again incremented Example: 3.0.0 -> 3.0.1 -> 3.0.2,
-etc are all stable releases from within the stable branch. 3.1.x is currently
-the main trunk, and where work on 3.2.x is taking place. If any questions,
-please post to the devel list before committing to a stable branch!
-
-Developers should remember too that if they commit a bugfix to the stable
-branch, this will more than likely require a separate submission to the main
-trunk, since these are separate development trees within CVS. If you are
-working on both, then this would require at least two separate check outs (i.e
-main trunk, and the stable release branch, which is v_3_0_branch at the
-moment).
-
-------------------------------------------------------------------------------
6.2. Before the Release: Freeze
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 3.0.1-stable-1 "New upstream version"
+ debchange -v 3.0.0-stable-1 "New upstream version"
Then, run:
dpkg-buildpackage -rfakeroot -us -uc -b
-This will create ../privoxy_3.0.1-stable-1_i386.deb which can be uploaded. To
+This will create ../privoxy_3.0.0-stable-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.
-3.0.1 (beta).
+3.0.0 (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.27 2002/12/01 06:31:58 hal9 Exp $
+$Id: faq.sgml,v 1.61.2.18 2002/08/14 16:39:37 hal9 Exp $
This FAQ gives quick answers to frequently asked questions about Privoxy. It
can't and doesn't replace the User Manual.
Privoxy is based on Internet Junkbuster (tm).
Please note that this document is constantly evolving. This copy represents the
-state at the release of version 0.0.0. You can find the latest version of the
+state at the release of version 3.0.0. 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.
2.1. Which browsers are supported by Privoxy?
2.2. Which operating systems are supported?
- 2.3. Can I use Privoxy with my email client?
- 2.4. Can I install Privoxy over Junkbuster?
- 2.5. I just installed Privoxy. Is there anything special I have to do now?
- 2.6. What is the proxy address of Privoxy?
- 2.7. I just installed Privoxy, and nothing is happening. All the ads are
+ 2.3. Can I install Privoxy over Junkbuster?
+ 2.4. I just installed Privoxy. Is there anything special I have to do now?
+ 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?
3. Configuration
3.5. How are actions files configured? What is the easiest way to do this?
3.6. There are several different "actions" files. What are the differences?
3.7. How can I make my Yahoo/Hotmail/GMX account work?
- 3.8. What's the difference between the "Cautious", "Medium" and "Radical"
+ 3.8. What's the difference between the "Cautious", "Medium" and "Advanced"
defaults?
3.9. Why can I change the configuration with a browser? Does that not raise
security issues?
3.17. Can I just set Privoxy to use port 80 and thus avoid individual
browser configuration?
3.18. Can Privoxy run as a "transparent" proxy?
- 3.19. How can I configure Privoxy for use with Outlook Express?
- 3.20. How can I have separate rules just for HTML mail?
- 3.21. How can I allow permanent cookies for my trusted sites?
4. Miscellaneous
4.17. Can Privoxy effect files that I download from a webserver? FTP
server?
4.18. Where can I find more information about Privoxy and related issues?
- 4.19. I've noticed that Privoxy changes "Microsoft" to "MicroSuck"! Why are
- you manipulating my browsing?
5. Troubleshooting
uninstall it. Now the finder tells me I don't have sufficient
privileges to empty the trash.
5.8. I get a completely blank page at one site. "View Source" shows only:
- <html><body></body></html>. Without Privoxy the page loads fine.
- 5.9. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?
+ <html><body></body></html>.
6. Contacting the developers, Bug Reporting and Feature Requests
The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make a name in
-their own right, especially now with the pending release of version 3.0.
+their own right.
-------------------------------------------------------------------------------
2.2. Which operating systems are supported?
At present, Privoxy is known to run on Windows(95, 98, ME, 2000, XP), Linux
-(RedHat, SuSE, Debian, Conectiva, Gentoo, Slackware), Mac OSX, OS/2, AmigaOS,
-BeOS, FreeBSD, NetBSD, OpenBSD, Solaris, and many more flavors of Unix.
+(RedHat, SuSE, Debian, Conectiva, Gentoo), Mac OSX, OS/2, AmigaOS, BeOS,
+FreeBSD, NetBSD, Solaris, and many more flavors of Unix.
But any operating system that runs TCP/IP, can conceivably take advantage of
Privoxy in a networked situation where Privoxy would run as a server on a LAN
-------------------------------------------------------------------------------
-2.3. Can I use Privoxy with my email client?
-
-As long as there is some way to set a HTTP proxy for the client, then yes, any
-application can be used, whether it is strictly speaking a "browser" or not.
-Though this may not be the best approach for dealing with some of the common
-abuses of HTML in email. See How can I configure Privoxy with Outlook Express?
-below for more on this.
-
-Be aware that HTML email presents a number of unique security and privacy
-related issues, that can require advanced skills to overcome. The developers
-recommend using email clients that can be configured to convert HTML to plain
-text for these reasons.
-
--------------------------------------------------------------------------------
-
-2.4. Can I install Privoxy over Junkbuster?
+2.3. Can I install Privoxy over Junkbuster?
We recommend you un-install Junkbuster first to minimize conflicts and
confusion. You may want to save your old configuration files for future
-------------------------------------------------------------------------------
-2.5. I just installed Privoxy. Is there anything special I have to do now?
+2.4. I just installed Privoxy. Is there anything special I have to do now?
All browsers must be told to use Privoxy as a proxy by specifying the correct
proxy address and port number in the appropriate configuration area for the
browser. See below. You should also flush your browser's memory and disk cache
-to get rid of any cached junk items, and remove any stored cookies.
+to get rid of any cached junk items.
-------------------------------------------------------------------------------
-2.6. What is the proxy address of Privoxy?
+2.5. What is the proxy address of Privoxy?
If you set up the Privoxy to run on the computer you browse from (rather than
your ISP's server or some networked computer on a LAN), the proxy will be on
-------------------------------------------------------------------------------
-2.7. I just installed Privoxy, and nothing is happening. All the ads are there.
+2.6. I just installed Privoxy, and nothing is happening. All the ads are there.
What's wrong?
Did you configure your browser to use Privoxy as a proxy? It does not sound
actions that might apply to any given site. As an example, if you are blocking
cookies as one of your default actions, but need to accept cookies from a given
site, you would need to define an exception for this site in one of your
-actions files, preferably in user.action.
+actions files, preferably in user.action
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-3.8. What's the difference between the "Cautious", "Medium" and "Radical"
+3.8. What's the difference between the "Cautious", "Medium" and "Advanced"
defaults?
Configuring Privoxy is not entirely trivial. To help you get started, we
-provide you with three different default action "profiles" in the web based
-actions file editor at http://config.privoxy.org/show-status. See the User
-Manual for a list of actions, and how the default profiles are set.
+provide you with three different default action "packages" in the web based
+actions file editor at http://config.privoxy.org/show-status. The following
+table shows you, which of the most important features are enabled in each
+configuration:
+
+Table 1. Default Configurations
+
++-----------------------------------------------------------------------------+
+|Feature |Cautious |Intermadiate |Advanced |
+|-------------------+------------------+-------------------+------------------|
+|Ad-blocking by URL |yes |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Ad-filtering by |yes |yes |yes |
+|size | | | |
+|-------------------+------------------+-------------------+------------------|
+|GIF de-animation |no |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Referer forging |no |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Cookie handling |none |session-only |kill |
+|-------------------+------------------+-------------------+------------------|
+|Pop-up killing |no |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Fast redirects |no |no |yes |
+|-------------------+------------------+-------------------+------------------|
+|HTML taming |yes |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|JavaScript taming |yes |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Web-bug killing |yes |yes |yes |
+|-------------------+------------------+-------------------+------------------|
+|Fun text |no |no |yes |
+|replacements | | | |
+|-------------------+------------------+-------------------+------------------|
+|Image tag |no |no |yes |
+|reordering | | | |
+|-------------------+------------------+-------------------+------------------|
+|Ad-filtering by |no |no |yes |
+|link | | | |
++-----------------------------------------------------------------------------+
Where the defaults are likely to break some sites, exceptions for known popular
"problem" sites are included, but in general, the more aggressive your default
-settings are, the more exceptions you will have to make later. See the User
-Manual for a more deatiled discussion.
-
-It should be noted that the "Radical" profile (formerly known as the "Advanced"
-profile) is not only more aggressive, but also includes fun and, extreme usage
-of most of Privoxy's features. Use at your own risk!
+settings are, the more exceptions you will have to make later. See the user
+manual for a more deatiled discussion.
-------------------------------------------------------------------------------
Save the file, and restart Privoxy. Configure all browsers on the network then
to use this address and port number.
-Alternately, you can have Privoxy listen on all available interfaces:
-
- listen-address :8118
-
-And then use Privoxy's permit-access feature to limit connections. A firewall
-in this situation is recommended as well.
-
-The above steps should be the same for any TCP network, regardless of operating
-system.
-
If you run Privoxy on a LAN with untrusted users, we recommend that you
double-check the access control and security options!
3.15. Can Privoxy run as a service on Win2K/NT?
-Yes, it can run as a system service using srvany.exe. See the discussion at
-http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=
-11118, for details, and a sample configuration.
+Yes, it can run as a system service using srvany.exe. The only catch is that
+this will effectively disable the Privoxy icon (and its menu!) in the taskbar.
+You can have one or the other, but not both at this time :(
-Version 3.0.1 fixes the problem where the icon and menu where not available in
-the taskbar for this usage.
+There is a pending feature request for this functionality. See the discussion
+at http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=
+11118, for details, and a sample configuration.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-3.19. How can I configure Privoxy for use with Outlook Express?
-
-Outlook Express uses Internet Explorer components to both render HTML, and
-fetch any HTTP requests that may be embedded in an HTML email. So however you
-have Privoxy configured to work with IE, this configuration should
-automatically be shared.
-
--------------------------------------------------------------------------------
-
-3.20. How can I have separate rules just for HTML mail?
-
-The short answer is, you can't. Privoxy has no way of knowing which particular
-application makes a request, so there is no way to distinguish between web
-pages and HTML mail. Privoxy just blindly proxies all requests. In the case of
-Outlook Express (see above), OE uses IE anyway, and there is no way for Privoxy
-to ever be able to distinguish between them (nor could any other proxy type
-application for that matter).
-
-For a good discussion of some of the issues involved (including privacy and
-security issues), see http://sourceforge.net/tracker/?func=detail&atid=211118&
-aid=629518&group_id=11118.
-
--------------------------------------------------------------------------------
-
-3.21. How can I allow permanent cookies for my trusted sites?
-
-There are several actions that relate to cookies. The default behavior is to
-allow only "session cookies", which means the cookies only last for the current
-browser session. This eliminates most kinds of abuse related to cookies. But
-there may be cases where we want cookies to last.
-
-To disable all cookie actions, so that cookies are allowed unrestricted, both
-in and out, for example.com:
-
- { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
- .example.com
-
-Place the above in user.action. Note some of these may be off by default
-anyway, so this might be redundant, but there is no harm being explicit in what
-you want to happen. user.action includes an alias for this situation, called
-allow-cookies.
-
--------------------------------------------------------------------------------
-
4. Miscellaneous
4.1. How much does Privoxy slow my browsing down? This has to add extra time to
server".
This also makes for a good test for your browser configuration: If entering the
-URL http://config.privoxy.org/ takes you to a page saying "This is Privoxy
-...", everything is OK. If you get a page saying "Privoxy is not working"
-instead, then your browser didn't use Privoxy for the request, hence it could
-not be intercepted, and you have accessed the real web site at
-config.privoxy.org.
+URL http://config.privoxy.org/ takes you to a page saying "This is Privoxy..",
+everything is OK. If you get a page saying "Privoxy is not working" instead,
+then your browser didn't use Privoxy for the request, hence it could not be
+intercepted, and you have accessed the real web site at config.privoxy.org.
With recent versions of Privoxy (version 2.9.x and later), the user interface
features information on the run time status, the configuration, and even a
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
-0.0.0.
+3.0.0.
-------------------------------------------------------------------------------
You can find a list of anonymous public proxies at multiproxy.org and many more
through Google. A particularly interesting project is the JAP service offered
by the Technical University of Dresden (http://anon.inf.tu-dresden.de/
-index_en.html).
+index_en.html.
There is, however, even in the single-machine case the possibility to make the
server believe that your machine is in fact a shared proxy serving a whole big
efficiency reasons, which exposes them to the full power of Privoxy's ad
blocking.
-"Content cookies" (those that are embedded in the actual HTML or JS page
-content, see filter{content-cookies}), in an SSL transaction will be impossible
-to block under these conditions. Fortunately, this does not seem to be a very
-common scenario since most cookies come by traditional means.
-
-------------------------------------------------------------------------------
4.13. Privoxy runs as a "server". How secure is it? Do I need to take any
-------------------------------------------------------------------------------
-4.19. I've noticed that Privoxy changes "Microsoft" to "MicroSuck"! Why are you
-manipulating my browsing?
-
-We're not. The text substitutions that you are seeing are disabled in the
-default configuration as shipped. You have either manually activated the "fun"
-filter which is clearly labeled "Text replacements for subversive browsing fun!
-" or you have implicitly activated it by choosing the "Radical" profile in the
-web-based editor (formerly known as the Advanced profile).
-
--------------------------------------------------------------------------------
-
5. Troubleshooting
5.1. I just upgraded and am getting "connection refused" with every web page?
to use Privoxy as an FTP proxy. The same is true for any protocol other than
HTTP or HTTPS.
-Most browsers understand FTP as well as HTTP. If you connect to a site, with a
-URL like ftp://ftp.example.com, your browser is making an FTP connection, and
-not a HTTP connection. So while your browser may speak FTP, Privoxy does not,
-and cannot proxy such traffic.
-
-------------------------------------------------------------------------------
5.6. In Mac OSX, I can't configure Microsoft Internet Explorer to use Privoxy
-------------------------------------------------------------------------------
5.8. I get a completely blank page at one site. "View Source" shows only:
-<html><body></body></html>. Without Privoxy the page loads fine.
+<html><body></body></html>.
-Chances are that the site suffers from a bug in PHP, which results in empty
-pages being sent if the client explicitly requests an uncompressed page, like
-Privoxy does. This bug has been fixed in PHP 4.2.3.
+This is often the result of a webserver using PHP that mishandles the request
+Privoxy sends to not compress the content (a PHP bug).
-To find out if this is in fact the source of the problem, try adding the site
-to a -prevent-compression section in user.action:
+In a default configuration, Privoxy requests all data be sent "uncompressed".
+This is required for the page filtering and other magic to work. In some rare
+cases, the browser and webserver miscommunicate and the result is a totally
+blank page. The suggested work around is to selectively turn off this feature
+for sites that exhibit such behavior. Example section for user.action:
# Make exceptions for ill-behaved sites:
#
{-prevent-compression}
.example.com
-If that works, you may also want to report the problem to the site's
-webmasters, telling them to use zlib.output_compression instead of ob_gzhandler
-in their PHP applications (workaround) or upgrade to PHP 4.2.3 or later (fix).
-
--------------------------------------------------------------------------------
-
-5.9. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?
-
-More than likely this is a problem with the network stack. ZoneAlarm has been
-reported to cause this symptom -- even if not running. The solution is to
-either fight the ZA configuration, or uninstall ZoneAlarm, and then find
-something better behaved in its place. Other firewall type products may cause
-similar type problems if not configured correctly.
-
-------------------------------------------------------------------------------
6. Contacting the developers, Bug Reporting and Feature Requests
-Privoxy 3.0.1 User Manual
+Privoxy 3.0.0 User Manual
Copyright © 2001, 2002 by Privoxy Developers
-$Id: user-manual.sgml,v 1.123.2.27 2003/03/18 19:37:14 oes Exp $
+$Id: user-manual.sgml,v 1.123.2.18 2002/08/22 23:47:58 hal9 Exp $
The User Manual gives users information on how to install, configure and use
Privoxy.
1. Introduction
This documentation is included with the current stable version of Privoxy,
-v.3.0.1.
+v.3.0.0.
-------------------------------------------------------------------------------
2.1.1. Red Hat, SuSE and Conectiva RPMs
-RPMs can be installed with rpm -Uvh privoxy-3.0.1-1.rpm, and will use /etc/
+RPMs can be installed with rpm -Uvh privoxy-3.0.0-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-3.0.1-1.src.rpm. This will use your locally installed
+--rebuild privoxy-3.0.0-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_3.0.1-1.deb, and will use /etc/
+DEBs can be installed with dpkg -i privoxy_3.0.0-1.deb, and will use /etc/
privoxy for the location of configuration files.
-------------------------------------------------------------------------------
latest version.
Configuration files are in /etc/privoxy, the documentation is in /usr/share/doc
-/privoxy-3.0.1 and the Log directory is in /var/log/privoxy.
+/privoxy-3.0.0 and the Log directory is in /var/log/privoxy.
-------------------------------------------------------------------------------
When building from a source tarball (either release version or nightly CVS
tarball), first unpack the source:
- tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz]
- cd privoxy-3.0.1
+ tar xzvf privoxy-3.0.0-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.0
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
This will create a directory named current/, which will contain the source
tree.
-You can also check out any Privoxy "branch", just exchange the current name
-with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs tree).
-
-It is also strongly recommended to not run Privoxy as root, and instead it is
-suggested to create a "privoxy" user and group for this purpose. See your local
-documentation for the correct command line to do this.
-
-/etc/passwd might then look like:
-
- privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell
-
-And then /etc/group, like:
-
- privoxy:*:7777:
-
-Some binary packages may do this for you.
-
-Then, to build from either unpacked tarball or CVS source:
+Then, in either case, to build from unpacked tarball or CVS source:
autoheader
autoconf
make # (the make from gnu, gmake for *BSD)
su
make -n install # (to see where all the files will go)
- make -s install # (to really install, -s to silence output)
+ make install # (to really install)
+
++-----------------------------------------------------------------------------+
+| Warning |
+|-----------------------------------------------------------------------------|
+|The "make install" target is temporary quite broken! It is recommended to use|
+|a binary package, or do a source build, and manually install the components. |
+|Sorry. |
++-----------------------------------------------------------------------------+
-If you have GNU make, you can have the first four steps automatically done for
+If you have gnu make, you can have the first four steps automatically done for
you by just typing:
make
in the freshly downloaded or unpacked source directory.
-WARNING: If installing as root, the install will fail unless another user is
-specified. configure accepts --with-user and --with-group options for setting
-user and group ownership of the configuration files (which need to be writable
-by the daemon). The specified user must already exist. Or if there is already a
-privoxy user on the system, and no user was specified during configure, make
-install then will use the privoxy user. When starting Privoxy, it should be run
-as this same user that owns the configuration and log files.
-
-Alternately, you can specify user and group on the make command line, but be
-sure both already exist:
-
- make -s install USER=privoxy GROUP=privoxy
-
-If no group is specified, the install will assume a group exists with the same
-name as the specified user.
-
-The default installation path for make install is /usr/local. This may of
-course be customized with the various ./configure path options. If you are
-doing a root install to anywhere else besides /usr/local, be sure to set the
-appropriate paths with the correct configure options (./configure --help).
-
-If you do install to /usr/local, the install will use sysconfdir=$prefix/etc/
-privoxy by default. All other destinations, and the direct usage of
---sysconfdir flag behave like normal, i.e. will not add the extra privoxy
-directory. This is for a safer install, as there may already exist another
-program that uses a file with the "config" name, and thus makes /usr/local/etc
-cleaner.
-
-If installing to /usr/local, the docs will go by default to $prefix/share/doc.
-But if this directory doesn't exist, it will then try $prefix/doc and install
-there before creating a new $prefix/share/doc just for Privoxy.
-
-Again, if the installs goes to /usr/local, the localstatedir (ie: var/) will
-default to /var instead of $prefix/var so the logs will go to /var/log/privoxy
-/, and the pid file will be created in /var/run/privoxy.pid.
-
-make install will attempt to set the correct values in config (main
-configuration file). You may want to check this to make sure all values are
-correct. If appropriate, an init script will be installed, but it is up to the
-user to determine how and where to start Privoxy. The init script should be
-checked for correct paths and values, if anything other than a default install
-is done.
-
-If install finds previous versions of any configuration files, these will not
-be overwritten, and the new ones will be installed with a "new" extension. You
-will then need to manually update the installed configuration files as needed.
-All template files will be overwritten. If you have customized, local
-templates, you should save these first. If a previous version of Privoxy is
-already running, you will have to restart it manually.
-
For more detailed instructions on how to build Redhat and SuSE RPMs, Windows
self-extracting installers, building on platforms with special requirements
etc, please consult the developer manual.
* Start Privoxy, if the installation program has not done this already (may
vary according to platform). See the section Starting Privoxy.
- * Set your browser to use Privoxy as HTTP and HTTPS (SSL) proxy by setting
- the proxy configuration for address of 127.0.0.1 and port 8118. (Junkbuster
- and earlier versions of Privoxy used port 8000.) See the section Starting
+ * Set your browser to use Privoxy as HTTP and HTTPS proxy by setting the
+ proxy configuration for address of 127.0.0.1 and port 8118. (Junkbuster and
+ earlier versions of Privoxy used port 8000.) See the section Starting
Privoxy below for more details on this.
* Flush your browser's disk and memory caches, to remove any cached ad
- images. If using Privoxy to manage cookies, you should remove any currently
- stored cookies too.
+ images.
* A default installation should provide a reasonable starting point for most.
There will undoubtedly be occasions where you will want to adjust the
included the GID of GROUP. Exit if the privileges are not sufficient to do
so. Unix only.
- * --chroot
-
- Before changing to the user ID given in the --user option, chroot to that
- user's home directory, i.e. make the kernel pretend to the Privoxy process
- that the directory tree starts there. If set up carefully, this can limit
- the impact of possible vulnerabilities in Privoxy to the files contained in
- that hierarchy. Unix only.
-
* configfile
If no configfile is included on the command line, Privoxy will look for a
Notes:
+ The windows version will additionally log to the console.
+
The logfile is where all logging and error messages are written. The level
of detail and number of messages are set with the debug option (see below).
The logfile can be useful for tracking down a problem with Privoxy (e.g.,
Effect if unset:
- The entire trust mechanism is turned off.
+ The whole trust mechanism is turned off.
Notes:
should be used with care. It is NOT recommended for the casual user.
If you specify a trust file, Privoxy will only allow access to sites that
- are specified in the trustfile. Sites can be listed in one of two ways:
-
- Prepending a ~ character limits access to this site only (and any sub-paths
- within this site), e.g. ~www.example.com.
+ are named in the trustfile. You can also mark sites as trusted referrers
+ (with +), with the effect that access to untrusted sites will be granted,
+ if a link from a trusted referrer was used. The link target will then be
+ added to the "trustfile". Possible applications include limiting Internet
+ access for children.
- Or, you can designate sites as trusted referrers, by prepending the name
- with a + character. The effect is that access to untrusted sites will be
- granted -- but only if a link from this trusted referrer was used. The link
- target will then be added to the "trustfile" so that future, direct
- accesses will be granted. Sites added via this mechanism do not become
- trusted referrers themselves (i.e. they are added with a ~ designation).
-
- If you use the + operator in the trust file, it may grow considerably over
+ If you use + operator in the trust file, it may grow considerably over
time.
- It is recommended that Privoxy be compiled with the --disable-force,
- --disable-toggle and --disable-editor options, if this feature is to be
- used.
-
- Possible applications include limiting Internet access for children.
-
-------------------------------------------------------------------------------
7.2. Local Set-up Documentation
Unix, in local filesystem:
- user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/
-
- Windows, in local filesystem, must use forward slash notation:
-
- user-manual file:/c:/some-dir/privoxy-3.0.1/user-manual/
-
- Windows, UNC notation (with forward slashes):
-
- user-manual file://///some-server/some-path/privoxy-3.0.1/user-manual/
+ user-manual file:///usr/share/doc/privoxy-3.0.0/user-manual/
Any platform, on local webserver (called "local-webserver"):
- user-manual http://local-webserver/privoxy-user-manual/
+ user-manual http://local-webserver/privoxy-user-manual/
+-----------------------------------------------------------------+
| Warning |
The actions files are used to define what actions Privoxy takes for which URLs,
and thus determine how ad images, cookies and various other aspects of HTTP
content and transactions are handled, and on which sites (or even parts
-thereof). There are three such files included with Privoxy with differing
-purposes:
+thereof). There are three such files included with Privoxy (as of version
+2.9.15), with differing purposes:
* default.action - is the primary action file that sets the initial values
for all actions. It is intended to provide a base level of functionality
influence on your browsing unless you select them explicitly in the editor.
It is not recommend to edit this file.
- The default profiles, and their associated actions, as pre-defined in
- standard.action are:
-
- Table 1. Default Configurations
-
- +-------------------------------------------------------------------------+
- |Feature |Cautious |Medium |Adventuresome |
- |------------------+-----------------+-----------------+------------------|
- |Ad-blocking by URL|yes |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |Ad-filtering by |yes |yes |yes |
- |size | | | |
- |------------------+-----------------+-----------------+------------------|
- |GIF de-animation |no |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |Referer forging |no |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |Cookie handling |none |session-only |kill |
- |------------------+-----------------+-----------------+------------------|
- |Pop-up killing |unsolicited |unsolicited |all |
- |------------------+-----------------+-----------------+------------------|
- |Fast redirects |no |no |yes |
- |------------------+-----------------+-----------------+------------------|
- |HTML taming |yes |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |JavaScript taming |yes |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |Web-bug killing |yes |yes |yes |
- |------------------+-----------------+-----------------+------------------|
- |Fun text |no |no |yes |
- |replacements | | | |
- |------------------+-----------------+-----------------+------------------|
- |Image tag |no |no |yes |
- |reordering | | | |
- |------------------+-----------------+-----------------+------------------|
- |Ad-filtering by |no |no |yes |
- |link | | | |
- |------------------+-----------------+-----------------+------------------|
- |Demoronizer |no |yes |yes |
- +-------------------------------------------------------------------------+
-
The list of actions files to be used are defined in the main configuration
-file, and are processed in the order they are defined (e.g. default.action is
-typically process before user.action). The content of these can all be viewed
-and edited from http://config.privoxy.org/show-status.
+file, and are processed in the order they are defined. The content of these can
+all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases"
in an actions file, you have to place the (optional) alias section at the top
right mix of actions is not always easy and certainly a matter of personal
taste. In general, it can be said that the more "aggressive" your default
settings (in the top section of the actions file) are, the more exceptions for
-"trusted" sites you will have to make later. If, for example, you want to
-crunch all cookies per default, you'll have to make exceptions from that rule
-for sites that you regularly use and that require cookies for actually useful
-puposes, like maybe your bank, favorite shop, or newspaper.
+"trusted" sites you will have to make later. If, for example, you want to kill
+popup windows per default, you'll have to make exceptions from that rule for
+sites that you regularly use and that require popups for actually useful
+content, like maybe your bank, favorite shop, or newspaper.
We have tried to provide you with reasonable rules to start from in the
distribution actions files. But there is no general rule of thumb on these
browser-based editor, which can be reached from http://config.privoxy.org/
show-status. The editor allows both fine-grained control over every single
feature on a per-URL basis, and easy choosing from wholesale sets of defaults
-like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome"
-setting is not only more aggressive, but includes settings that are fun and
-subversive, and which some may find of dubious merit!
+like "Cautious", "Medium" or "Advanced".
If you prefer plain text editing to GUIs, you can of course also directly edit
the the actions files. Look at default.action which is richly commented.
8.4. Patterns
-As mentioned, Privoxy uses "patterns" to determine what actions might apply to
-which sites and pages your browser attempts to access. These "patterns" use
-wild card type pattern matching to achieve a high degree of flexibility. This
-allows one expression to be expanded and potentially match against many similar
-patterns.
-
-Generally, a Privoxy pattern has the form <domain>/<path>, where both the
-<domain> and <path> are optional. (This is why the special / pattern matches
-all URLs). Note that the protocol portion of the URL pattern (e.g. http://)
-should not be included in the pattern. This is assumed already!
+Generally, a pattern has the form <domain>/<path>, where both the <domain> and
+<path> are optional. (This is why the pattern / matches all URLs).
www.example.com/
It makes no sense at all to use this action in conjunction with the
session-cookies-only action, since it would prevent the session cookies
- from being set. See also filter-content-cookies.
+ from being set.
Example usage:
The amount of data that can be filtered is limited to the buffer-limit
option in the main config file. The default is 4096 KB (4 Megs). Once this
limit is exceeded, the buffered data, and all pending data, is passed
- through unfiltered.
-
- Inappropriate MIME types, such as zipped files, are not filtered at all.
- Encrypted SSL data (from HTTPS servers) cannot be filtered either since
- this would violate the integrity of the secure transaction.
+ through unfiltered. Inappropriate MIME types are not filtered.
At this time, Privoxy cannot (yet!) uncompress compressed documents. If you
want filtering to work on all documents, even those that would normally be
Example usage (with filters from the distribution default.filter file):
- +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse
+ +filter{html-annoyances} # Get rid of particularly annoying HTML abuse.
- +filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)
-
- +filter{html-annoyances} # Get rid of particularly annoying HTML abuse
-
- +filter{content-cookies} # Kill cookies that come in the HTML or JS content
-
- +filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)
+ +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse
- +filter{unsolicited-popups} # Disable only unsolicited pop-up windows
+ +filter{banners-by-size} # Kill banners based on their size for this page (very efficient!)
- +filter{all-popups} # Kill all popups in JavaScript and HTML
+ +filter{banners-by-link} # Kill banners based on the link they are contained in (experimental)
+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective
- +filter{banners-by-size} # Kill banners by size
+ +filter{content-cookies} # Kill cookies that come sneaking in the HTML or JS content
- +filter{banners-by-link} # Kill banners by their links to known clicktrackers
+ +filter{popups} # Kill all popups in JS and HTML
+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)
- +filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap
+ +filter{fun} # Text replacements for subversive browsing fun!
- +filter{jumping-windows} # Prevent windows from resizing and moving themselves
+ +filter{frameset-borders} # Give frames a border and make them resizeable
- +filter{frameset-borders} # Give frames a border and make them resizable
+ +filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)
- +filter{demoronizer} # Fix MS's non-standard use of standard charsets
+ +filter{nimda} # Remove Nimda (virus) code.
+filter{shockwave-flash} # Kill embedded Shockwave Flash objects
- +filter{quicktime-kioskmode} # Make Quicktime movies saveable
-
- +filter{fun} # Text replacements for subversive browsing fun!
+ +filter{crude-parental} # Kill all web pages that contain the words "sex" or "warez"
- +filter{crude-parental} # Crude parental filtering (demo only)
-
- +filter{ie-exploits} # Disable some known Internet Explorer bug exploits
+ +filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)
-------------------------------------------------------------------------------
Typical use:
- Eliminate those annoying pop-up windows (deprecated)
+ Eliminate those annoying pop-up windows
Effect:
Notes:
- This action is basically a built-in, hardwired special-purpose filter
- action, but there are important differences: For kill-popups, the document
- need not be buffered, so it can be incrementally rendered while
- downloading. But kill-popups doesn't catch as many pop-ups as filter
- {all-popups} does and is not as smart as filter{unsolicited-popups} is.
+ This action is easily confused with the built-in, hardwired filter action,
+ but there are important differences: For kill-popups, the document need not
+ be buffered, so it can be incrementally rendered while downloading. But
+ kill-popups doesn't catch as many pop-ups as filter{popups} does.
Think of it as a fast and efficient replacement for a filter that you can
use if you don't want any filtering at all. Note that it doesn't make sense
the whole document needs to be buffered anyway, which destroys the
advantage of the kill-popups action over its filter equivalent.
- Killing all pop-ups unconditionally is problematic. Many shops and banks
- rely on pop-ups to display forms, shopping carts etc, and the filter
- {unsolicited-popups} does a fairly good job of catching only the unwanted
- ones.
-
- If the only kind of pop-ups that you want to kill are exit consoles (those
- really nasty windows that appear when you close an other one), you might
- want to use filter{js-annoyances} instead.
+ Killing all pop-ups is a dangerous business. Many shops and banks rely on
+ pop-ups to display forms, shopping carts etc, and killing only the unwanted
+ pop-ups would require artificial intelligence in Privoxy. If the only kind
+ of pop-ups that you want to kill are exit consoles (those really nasty
+ windows that appear when you close an other one), you might want to use
+ filter{js-annoyances} instead.
Example usage:
"expires" field. If you use an exotic browser, you might want to try it out
to be sure.
- This setting also has no effect on cookies that may have been stored
- previously by the browser before starting Privoxy. These would have to be
- removed manually.
-
- Privoxy also uses the content-cookies filter to block some types of
- cookies. Content cookies are not effected by session-cookies-only.
-
Example usage:
+session-cookies-only
Now let's define some aliases...
- # Useful custom aliases we can use later.
- #
- # Note the (required!) section header line and that this section
- # must be at the top of the actions file!
- #
- {{alias}}
-
- # These aliases just save typing later:
- # (Note that some already use other aliases!)
- #
- +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
- -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- block-as-image = +block +handle-as-image
- mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies}
-
- # These aliases define combinations of actions
- # that are useful for certain types of sites:
- #
- fragile = -block -filter -crunch-all-cookies -fast-redirects -hide-referrer -kill-popups
- shop = -crunch-all-cookies -filter{all-popups} -kill-popups
-
- # Short names for other aliases, for really lazy people ;-)
- #
- c0 = +crunch-all-cookies
- c1 = -crunch-all-cookies
+ # Useful custom aliases we can use later.
+ #
+ # Note the (required!) section header line and that this section
+ # must be at the top of the actions file!
+ #
+ {{alias}}
+
+ # These aliases just save typing later:
+ # (Note that some already use other aliases!)
+ #
+ +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
+ -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
+ block-as-image = +block +handle-as-image
+ mercy-for-cookies = -crunch-all-cookies -session-cookies-only
+
+ # These aliases define combinations of actions
+ # that are useful for certain types of sites:
+ #
+ fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
+ shop = -crunch-all-cookies -filter{popups} -kill-popups
+
+ # Short names for other aliases, for really lazy people ;-)
+ #
+ c0 = +crunch-all-cookies
+ c1 = -crunch-all-cookies
...and put them to use. These sections would appear in the lower part of an
actions file and define exceptions to the default actions (as specified further
# These shops require pop-ups:
#
- {shop -kill-popups -filter{all-popups}}
+ {shop -kill-popups -filter{popups}}
.dabs.com
.overclockers.co.uk
from the above chapter on aliases, that also explains why and how aliases are
used:
-##########################################################################
-# Aliases
-##########################################################################
-{{alias}}
-
- # These aliases just save typing later:
- # (Note that some already use other aliases!)
- #
- +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
- -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- block-as-image = +block +handle-as-image
- mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies}
-
- # These aliases define combinations of actions
- # that are useful for certain types of sites:
- #
- fragile = -block -filter -crunch-all-cookies -fast-redirects -hide-referrer -kill-popups
- shop = -crunch-all-cookies -filter{all-popups} -kill-popups
+##########################################################################
+# Aliases
+##########################################################################
+{{alias}}
+
+# These aliases just save typing later:
+# (Note that some already use other aliases!)
+#
++crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
+-crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
+block-as-image = +block +handle-as-image
+mercy-for-cookies = -crunch-all-cookies -session-cookies-only
+
+# These aliases define combinations of actions
+# that are useful for certain types of sites:
+#
+fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
+shop = mercy-for-cookies -filter{popups} -kill-popups
Now come the regular sections, i.e. sets of actions, accompanied by URL
patterns to which they apply. Remember all actions are disabled when matching
+deanimate-gifs \
-downgrade-http-version \
+fast-redirects \
- +filter{js-annoyances} \
- -filter{js-events} \
+filter{html-annoyances} \
+ +filter{js-annoyances} \
-filter{content-cookies} \
- +filter{refresh-tags} \
- +filter{unsolicited-popups} \
- -filter{all-popups} \
- +filter{img-reorder} \
+ +filter{popups} \
+ +filter{webbugs} \
+ -filter{refresh-tags} \
+ -filter{fun} \
+ +filter{nimda} \
+filter{banners-by-size} \
-filter{banners-by-link} \
- +filter{webbugs} \
- -filter{tiny-textforms} \
- +filter{jumping-windows} \
- -filter{frameset-borders} \
- +filter{demoronizer} \
+ -filter{img-reorder} \
-filter{shockwave-flash} \
- -filter{quicktime-kioskmode} \
- -filter{fun} \
-filter{crude-parental} \
- +filter{ie-exploits} \
+ -filter{js-events} \
-handle-as-image \
+hide-forwarded-for-headers \
+hide-from-header{block} \
user agent, are part of a "general policy" that applies universally and won't
get any exceptions defined later. Other choices, like not blocking (which is
understandably the default!) need exceptions, i.e. we need to specify
-explicitly what we want to block in later sections.
+explicitly what we want to block in later sections. We will also want to make
+exceptions from our general pop-up-killing, and use our defined aliases for
+that.
The first of our specialized sections is concerned with "fragile" sites, i.e.
sites that require minimum interference, because they are either very complex
.jungle.com
.scan.co.uk
+Then, there are sites which rely on pop-up windows (yuck!) to work. Since we
+made pop-up-killing our default above, we need to make exceptions now. Mozilla
+users, who can turn on smart handling of unwanted pop-ups in their browsers,
+can safely choose -filter{popups} (and -kill-popups) above and hence don't need
+this section. Anyway, disabling an already disabled action doesn't hurt, so
+we'll define our exceptions regardless of what was chosen in the defaults
+section:
+
+# These sites require pop-ups too :(
+#
+{ -kill-popups -filter{popups} }
+.dabs.com
+.overclockers.co.uk
+.deutsche-bank-24.de
+
The fast-redirects action, which we enabled per default above, breaks some
sites. So disable it for popular sites where we know it misbehaves:
As aliases are local to the actions file that they are defined in, you can't
use the ones from default.action, unless you repeat them here:
-# Aliases are local to the file they are defined in.
# (Re-)define aliases for this file:
#
{{alias}}
-#
-# These aliases just save typing later, and the alias names should
-# be self explanatory.
-#
-+crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
-crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- allow-all-cookies = -crunch-all-cookies -session-cookies-only
- allow-popups = -filter{all-popups} -kill-popups
-+block-as-image = +block +handle-as-image
--block-as-image = -block
-
-# These aliases define combinations of actions that are useful for
-# certain types of sites:
-#
+mercy-for-cookies = -crunch-all-cookies -session-cookies-only
fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
-shop = -crunch-all-cookies allow-popups
-
-# Allow ads for selected useful free sites:
-#
-allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
+shop = mercy-for-cookies -filter{popups} -kill-popups
+allow-ads = -block -filter{banners-by-size} # (see below)
Say you have accounts on some sites that you visit regularly, and you don't
want to have to log in manually each time. So you'd like to allow persistent
-cookies for these sites. The allow-all-cookies alias defined above does exactly
-that, i.e. it disables crunching of cookies in any direction, and the
-processing of cookies to make them only temporary.
+cookies for these sites. The mercy-for-cookies alias defined above does exactly
+that, i.e. it disables crunching of cookies in any direction, and processing of
+cookies to make them temporary.
-{ allow-all-cookies }
+{ mercy-for-cookies }
sunsolve.sun.com
slashdot.org
.yahoo.com
.msdn.microsoft.com
.redhat.com
-Your bank is allergic to some filter, but you don't know which, so you disable
-them all:
+Your bank needs popups and is allergic to some filter, but you don't know
+which, so you disable them all:
-{ -filter }
+{ -filter -kill-popups }
.your-home-banking-site.com
-Some file types you may not want to filter. Privoxy makes no distinctions
-between regular web pages and downloads done via your web browser if it is an
-html or text type document.
-
-# A list of common file extensions that are likely to indicate raw text, and best
-# if unfiltered.
-/(.*/)?.*\.(pl|(s|p)?h|c(c|xx|pp)?|tcl|am|init?|cfg?|conf(ig)?|txt|rc|bat)$
-
-# Documentation should not need filtering (at least on some sites).
-.tldp.org
-
-Example of a simple block action. Say you've seen an ad on your favourite page
-on example.com that you want to get rid of. You have right-clicked the image,
-selected "copy image location" and pasted the URL below while removing the
-leading http://, into a { +block } section. Note that { +handle-as-image } need
-not be specified, since all URLs ending in .gif will be tagged as images by the
-general rules as set in default.action anyway:
+While browsing the web with Privoxy you noticed some ads that sneaked through,
+but you were too lazy to report them through our fine and easy feedback system,
+so you have added them here:
{ +block }
-www.example.com/nasty-ads/sponsor.gif
+www.a-popular-site.com/some/unobvious/path
another.popular.site.net/more/junk/here/
-
-# Here we found one that is not in Privoxy's default blocked list:
-.adfactory.net
-
-To force URLs that tend to have ad images, but it is difficult for Privoxy to
-know this since the ultimate returned object is obscured for one reason or
-another, we can try to force these to be treated as images (and thus avoid
-Privoxy's "BLOCKED" banner page). Note that if what is returned by the server
-turns out NOT to be an image, then your browser typically will display a broken
-icon image. Use cautiously.
-
-{ +block-as-image }
-# A shockwave ad, very annoying.
-.trip.com/.*\.swf
-.doubleclick.net
-/Realmedia/ads/
-adremote.
-
-Now you noticed that the default configuration breaks Forbes Magazine, but you
+
+Note that, assuming the banners in the above example have regular image
+extensions (most do), +handle-as-image need not be specified, since all URLs
+ending in these extensions will already have been tagged as images in the
+relevant section of default.action by now.
+
+Then you noticed that the default configuration breaks Forbes Magazine, but you
were too lazy to find out which action is the culprit, and you were again too
lazy to give feedback, so you just used the fragile alias on the site, and --
-whoa! -- it worked. The fragile aliases disables those actions that are most
-likely to break a site. Also, good for testing purposes to see if it is Privoxy
-that is causing the problem or not.
+whoa! -- it worked:
{ fragile }
.forbes.com
code on CVS->Web interfaces. Since user.action has the last word, these
exceptions won't be valid for the "fun" filtering specified here.
-You might also worry about how your favourite free websites are funded, and
+Finally, you might think about how your favourite free websites are funded, and
find that they rely on displaying banner advertisements to survive. So you
might want to specifically allow banners for those sites that you feel provide
value to you:
.slashdot.org
.osdn.net
-Note that allow-ads has been aliased to -block, -filter{banners-by-size}, and -
-filter{banners-by-link} above.
-
-user.action is generally the best place to define exceptions and additions to
-the default policies of default.action. Some actions are safe to have their
-default policies set here though. So let's set a default policy to have a
-"blank" image as opposed to the checkerboard pattern for ALL sites. "/" of
-course matches all URL paths and patterns:
-
-{ +set-image-blocker{blank} }
-/ # ALL sites
+Note that allow-ads has been aliased to -block -filter{banners-by-size} above.
-------------------------------------------------------------------------------
Current Project Contributors:
- Johny Agotnes
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
Hal Burgiss (docs)
- Mattes Dolak
Karsten Hopp (Red Hat)
Alexander Lazic
- Daniel Leite
Gábor Lipták
- Andrew Lock (Win32)
- Guy Laroche
+ Guy
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
David Schmidt (OS/2, Mac OSX ports)
Joerg Strohmayer (Amiga)
- Sviatoslav Sviridov
Sarantis Paskalis
Based in part on code originally developed by:
Andrew J. Caines
Clifford Caoile
Michael T. Davis
- Brian Dessent
Peter E
Aaron Hamid
Magnus Holmgren
- Don Libes
+ Daniel Leite
Paul Lieverse
- David Mediavilla
- Oliver Stoeneberg
Roberto Ragusa
Maynard Riley
Bart Schelstraete
Darren Wiebe
- Jamie Zawinski
+ jwz
-------------------------------------------------------------------------------
><H1
CLASS="SECT1"
><A
-NAME="CODING"
-></A
->4. Coding Guidelines</H1
+NAME="CODING">4. Coding Guidelines</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="S1"
-></A
->4.1. Introduction</H2
+NAME="S1">4.1. Introduction</H2
><P
>This set of standards is designed to make our lives easier. It is
developed with the simple goal of helping us keep the "new and improved
><H2
CLASS="SECT2"
><A
-NAME="S2"
-></A
->4.2. Using Comments</H2
+NAME="S2">4.2. Using Comments</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S3"
-></A
->4.2.1. Comment, Comment, Comment</H3
+NAME="S3">4.2.1. Comment, Comment, Comment</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S4"
-></A
->4.2.2. Use blocks for comments</H3
+NAME="S4">4.2.2. Use blocks for comments</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S5"
-></A
->4.2.3. Keep Comments on their own line</H3
+NAME="S5">4.2.3. Keep Comments on their own line</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S6"
-></A
->4.2.4. Comment each logical step</H3
+NAME="S6">4.2.4. Comment each logical step</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S7"
-></A
->4.2.5. Comment All Functions Thoroughly</H3
+NAME="S7">4.2.5. Comment All Functions Thoroughly</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S8"
-></A
->4.2.6. Comment at the end of braces if the
+NAME="S8">4.2.6. Comment at the end of braces if the
content is more than one screen length</H3
><P
><SPAN
><H2
CLASS="SECT2"
><A
-NAME="S9"
-></A
->4.3. Naming Conventions</H2
+NAME="S9">4.3. Naming Conventions</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S10"
-></A
->4.3.1. Variable Names</H3
+NAME="S10">4.3.1. Variable Names</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S11"
-></A
->4.3.2. Function Names</H3
+NAME="S11">4.3.2. Function Names</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S12"
-></A
->4.3.3. Header file prototypes</H3
+NAME="S12">4.3.3. Header file prototypes</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S13"
-></A
->4.3.4. Enumerations, and #defines</H3
+NAME="S13">4.3.4. Enumerations, and #defines</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S14"
-></A
->4.3.5. Constants</H3
+NAME="S14">4.3.5. Constants</H3
><P
><SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="S15"
-></A
->4.4. Using Space</H2
+NAME="S15">4.4. Using Space</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S16"
-></A
->4.4.1. Put braces on a line by themselves.</H3
+NAME="S16">4.4.1. Put braces on a line by themselves.</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S17"
-></A
->4.4.2. ALL control statements should have a
+NAME="S17">4.4.2. ALL control statements should have a
block</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S18"
-></A
->4.4.3. Do not belabor/blow-up boolean
+NAME="S18">4.4.3. Do not belabor/blow-up boolean
expressions</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S19"
-></A
->4.4.4. Use white space freely because it is
+NAME="S19">4.4.4. Use white space freely because it is
free</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S20"
-></A
->4.4.5. Don't use white space around structure
+NAME="S20">4.4.5. Don't use white space around structure
operators</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S21"
-></A
->4.4.6. Make the last brace of a function stand
+NAME="S21">4.4.6. Make the last brace of a function stand
out</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S22"
-></A
->4.4.7. Use 3 character indentions</H3
+NAME="S22">4.4.7. Use 3 character indentions</H3
><P
><SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="S23"
-></A
->4.5. Initializing</H2
+NAME="S23">4.5. Initializing</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S24"
-></A
->4.5.1. Initialize all variables</H3
+NAME="S24">4.5.1. Initialize all variables</H3
><P
><SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="S25"
-></A
->4.6. Functions</H2
+NAME="S25">4.6. Functions</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S26"
-></A
->4.6.1. Name functions that return a boolean as a
+NAME="S26">4.6.1. Name functions that return a boolean as a
question.</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S27"
-></A
->4.6.2. Always specify a return type for a
+NAME="S27">4.6.2. Always specify a return type for a
function.</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S28"
-></A
->4.6.3. Minimize function calls when iterating by
+NAME="S28">4.6.3. Minimize function calls when iterating by
using variables</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S29"
-></A
->4.6.4. Pass and Return by Const Reference</H3
+NAME="S29">4.6.4. Pass and Return by Const Reference</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S30"
-></A
->4.6.5. Pass and Return by Value</H3
+NAME="S30">4.6.5. Pass and Return by Value</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S31"
-></A
->4.6.6. Names of include files</H3
+NAME="S31">4.6.6. Names of include files</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S32"
-></A
->4.6.7. Provide multiple inclusion
+NAME="S32">4.6.7. Provide multiple inclusion
protection</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S33"
-></A
->4.6.8. Use `extern "C"` when appropriate</H3
+NAME="S33">4.6.8. Use `extern "C"` when appropriate</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S34"
-></A
->4.6.9. Where Possible, Use Forward Struct
+NAME="S34">4.6.9. Where Possible, Use Forward Struct
Declaration Instead of Includes</H3
><P
><SPAN
><H2
CLASS="SECT2"
><A
-NAME="S35"
-></A
->4.7. General Coding Practices</H2
+NAME="S35">4.7. General Coding Practices</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="S36"
-></A
->4.7.1. Turn on warnings</H3
+NAME="S36">4.7.1. Turn on warnings</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S37"
-></A
->4.7.2. Provide a default case for all switch
+NAME="S37">4.7.2. Provide a default case for all switch
statements</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S38"
-></A
->4.7.3. Try to avoid falling through cases in a
+NAME="S38">4.7.3. Try to avoid falling through cases in a
switch statement.</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S39"
-></A
->4.7.4. Use 'long' or 'short' Instead of
+NAME="S39">4.7.4. Use 'long' or 'short' Instead of
'int'</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S40"
-></A
->4.7.5. Don't mix size_t and other types</H3
+NAME="S40">4.7.5. Don't mix size_t and other types</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S41"
-></A
->4.7.6. Declare each variable and struct on its
+NAME="S41">4.7.6. Declare each variable and struct on its
own line.</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S42"
-></A
->4.7.7. Use malloc/zalloc sparingly</H3
+NAME="S42">4.7.7. Use malloc/zalloc sparingly</H3
><P
><SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="S43"
-></A
->4.7.8. The Programmer Who Uses 'malloc' is
+NAME="S43">4.7.8. The Programmer Who Uses 'malloc' is
Responsible for Ensuring 'free'</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S44"
-></A
->4.7.9. Add loaders to the `file_list' structure
+NAME="S44">4.7.9. Add loaders to the `file_list' structure
and in order</H3
><P
><SPAN
><H3
CLASS="SECT3"
><A
-NAME="S45"
-></A
->4.7.10. "Uncertain" new code and/or changes to
+NAME="S45">4.7.10. "Uncertain" new code and/or changes to
existing code, use FIXME</H3
><P
><SPAN
><H2
CLASS="SECT2"
><A
-NAME="S46"
-></A
->4.8. Addendum: Template for files and function
+NAME="S46">4.8. Addendum: Template for files and function
comment blocks:</H2
><P
><SPAN
><TD
><PRE
CLASS="PROGRAMLISTING"
->const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 Exp $";
+>const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.46.2.8 2002/08/17 00:16:10 hal9 Exp $";
/*********************************************************************
*
* File : $Source$
CLASS="PROGRAMLISTING"
>#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.46.2.8 2002/08/17 00:16:10 hal9 Exp $"
/*********************************************************************
*
* File : $Source$
><H1
CLASS="SECT1"
><A
-NAME="CONTACT"
-></A
->8. Contacting the developers, Bug Reporting and Feature Requests</H1
+NAME="CONTACT">8. Contacting the developers, Bug Reporting and Feature Requests</H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT"
-></A
->8.1. Get Support</H2
+NAME="CONTACT-SUPPORT">8.1. Get Support</H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS"
-></A
->8.2. Report Bugs</H2
+NAME="CONTACT-BUGS">8.2. Report Bugs</H2
><P
> Please report all bugs <SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE"
-></A
->8.3. Request New Features</H2
+NAME="CONTACT-FEATURE">8.3. Request New Features</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"
-></A
->8.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS">8.4. Report Ads or Other Actions-Related Problems</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"
-></A
->8.5. Other</H2
+NAME="CONTACT-OTHER">8.5. Other</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!
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT"
-></A
->9. Privoxy Copyright, License and History</H1
+NAME="COPYRIGHT">9. Privoxy Copyright, License and History</H1
><P
> Copyright © 2001, 2002 by Privoxy Developers <TT
CLASS="EMAIL"
><H2
CLASS="SECT2"
><A
-NAME="AEN1177"
-></A
->9.1. License</H2
+NAME="AEN1156">9.1. License</H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN1193"
-></A
->9.2. History</H2
+NAME="AEN1172">9.2. History</H2
><P
> In the beginning, there was the
<A
><H1
CLASS="SECT1"
><A
-NAME="CVS"
-></A
->2. The CVS Repository</H1
+NAME="CVS">2. The CVS Repository</H1
><P
-> If you become part of the active development team, you will eventually
- need write access to our holy grail, the CVS repository. One of the
- team members will need to set this up for you. Please read
- this chapter completely before accessing via CVS.
+> If you intend to help us with programming, documentation or packaging
+ you will need write access to our holy grail, the CVS repository.
+ Please read this chapter completely before accessing via CVS.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="CVSACCESS"
-></A
->2.1. Access to CVS</H2
+NAME="CVSACCESS">2.1. Access to CVS</H2
><P
> The project's CVS repository is hosted on
<A
><H2
CLASS="SECT2"
><A
-NAME="CVSBRANCHES"
-></A
->2.2. Branches</H2
-><P
-> Within the CVS repository, there are modules and branches. As
- mentioned, the sources are in the <TT
-CLASS="LITERAL"
->current</TT
->
- <SPAN
-CLASS="QUOTE"
->"module"</SPAN
->. Other modules are present for platform specific
- issues. There is a webview of the CVS hierarchy at <A
-HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/"
-TARGET="_top"
->http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/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
-> This will result in at least two active branches, which means there may
- be occasions that require the same (or similar) item to be
- checked into to two different places (assuming its a bugfix and needs
- fixing in both the stable and unstable trees). This also means that in
- order to have access to both trees, both will have to be checked out
- separately. Use the <TT
-CLASS="LITERAL"
->cvs -r</TT
-> flag to check out a
- branch, e.g: <TT
-CLASS="LITERAL"
->cvs co -r v_3_0_branch current</TT
->.
- </P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="CVSCOMMIT"
-></A
->2.3. CVS Commit Guidelines</H2
+NAME="CVSCOMMIT">2.2. CVS Commit Guideline</H2
><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
-><P
-> Basic Guidelines, for all branches:
- </P
-><P
-> <P
+ times. We therefore ask anyone with CVS access to strictly adhere to the
+ following guidelines:
+ <P
></P
><UL
><LI
><LI
><P
> Before changing things on CVS, make sure that your changes are in line
- with the team's general consensus on what should be done.
+ with the team's general consensus on what should be done (see below).
</P
></LI
><LI
><P
-> Note that near a major public release, we get more cautious.
- There is always the possibility to submit a patch to the <A
+> 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"
->patch
+>patches
tracker</A
> instead.
</P
></UL
>
</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="CVSWHENASK">2.3. Discussing Changes First</H2
><P
-> Stable branches are handled with more care, especially after the
- initial *.*.0 release, and we are just in bugfix mode. In addition to
- the above, the below applies only to the stable branch (currently the
- <TT
-CLASS="LITERAL"
->v_3_0_branch</TT
-> branch):
- </P
-><P
-> <P
+> We don't have a too formal policy on this, just use common sense. Hints: If it is..
+ <P
></P
-><UL
+><OL
+TYPE="1"
><LI
><P
-> Do not commit <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->anything</I
-></SPAN
-> unless your proposed
- changes have been well tested first, preferably by other members of the
- project, or have prior approval of the project leaders or consensus
- of the devel list.
- </P
+> ..a bug-fix / clean-up / cosmetic thing: shoot
+ </P
></LI
><LI
><P
-> Where possible, bugfixes and changes should be tested in the main
- development trunk first. There may be occasions where this is not
- feasible, though.
- </P
+> ..a new feature that can be turned off: shoot
+ </P
></LI
><LI
><P
-> Alternately, proposed changes can be submitted as patches to the patch tracker on
- Sourceforge first: <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=311118"
+> ..a clear improvement w/o side effects on other parts of the code: shoot
+ </P
+></LI
+><LI
+><P
+> ..a matter of taste: <A
+HREF="mailto:developers@privoxy.org"
TARGET="_top"
->http://sourceforge.net/tracker/?group_id=11118&atid=311118</A
->.
- Then ask for peer review.
- </P
+>ask the list</A
+>
+ </P
></LI
><LI
><P
-> Do not even think about anything except bugfixes. No new features!
- </P
+> ..a major redesign of some part of the code: <A
+HREF="mailto:developers@privoxy.org"
+TARGET="_top"
+>ask
+ the list</A
+>
+ </P
></LI
-></UL
+></OL
>
</P
+><P
+> Note that near a major public release, we get a bit more cautious - if
+ unsure, it doesn't hurt to ask first. There is always the possibility
+ to submit a patch to the <A
+HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
+TARGET="_top"
+>patches
+ tracker</A
+> instead.
+ </P
></DIV
></DIV
><DIV
><H1
CLASS="SECT1"
><A
-NAME="DOCUMENTATION"
-></A
->3. Documentation Guidelines</H1
+NAME="DOCUMENTATION">3. Documentation Guidelines</H1
><P
> All formal documents are maintained in Docbook SGML and located in the
<TT
><H2
CLASS="SECT2"
><A
-NAME="SGML"
-></A
->3.1. Quickstart to Docbook and SGML</H2
+NAME="SGML">3.1. Quickstart to Docbook and SGML</H2
><P
> If you are not familiar with SGML, it is a markup language similar to HTML.
Actually, not a mark up language per se, but a language used to define
><H2
CLASS="SECT2"
><A
-NAME="DOCSTYLE"
-></A
->3.2. <SPAN
+NAME="DOCSTYLE">3.2. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> Documentation Style</H2
><H2
CLASS="SECT2"
><A
-NAME="AEN233"
-></A
->3.3. Privoxy Custom Entities</H2
+NAME="AEN222">3.3. Privoxy Custom Entities</H2
><P
> <SPAN
CLASS="APPLICATION"
>
version string, e.g. <SPAN
CLASS="QUOTE"
->"3.0.1"</SPAN
+>"3.0.0"</SPAN
>.
</TD
></TR
><H1
CLASS="TITLE"
><A
-NAME="AEN2"
-></A
->Privoxy Developer Manual</H1
+NAME="AEN2">Privoxy Developer Manual</H1
><P
CLASS="PUBDATE"
> <SUB
<BR></P
><P
CLASS="PUBDATE"
->$Id: developer-manual.sgml,v 1.46.2.11 2002/12/11 13:12:15 hal9 Exp $<BR></P
+>$Id: developer-manual.sgml,v 1.46.2.8 2002/08/17 00:16:10 hal9 Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"
-></A
-><P
+NAME="AEN9"><P
></P
><P
> The developer manual provides guidance on coding, testing, packaging, documentation
for anyone who wants to join the team.</P
><P
> Please note that this document is constantly evolving. This copy represents
- the state at the release of version 3.0.1.
+ the state at the release of version 3.0.0.
You can find the latest version of the this manual at <A
HREF="http://www.privoxy.org/developer-manual/"
TARGET="_top"
></DT
><DT
>2.2. <A
-HREF="cvs.html#CVSBRANCHES"
->Branches</A
+HREF="cvs.html#CVSCOMMIT"
+>CVS Commit Guideline</A
></DT
><DT
>2.3. <A
-HREF="cvs.html#CVSCOMMIT"
->CVS Commit Guidelines</A
+HREF="cvs.html#CVSWHENASK"
+>Discussing Changes First</A
></DT
></DL
></DD
></DT
><DT
>3.3. <A
-HREF="documentation.html#AEN233"
+HREF="documentation.html#AEN222"
>Privoxy Custom Entities</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="copyright.html#AEN1177"
+HREF="copyright.html#AEN1156"
>License</A
></DT
><DT
>9.2. <A
-HREF="copyright.html#AEN1193"
+HREF="copyright.html#AEN1172"
>History</A
></DT
></DL
><H1
CLASS="SECT1"
><A
-NAME="INTRODUCTION"
-></A
->1. Introduction</H1
+NAME="INTRODUCTION">1. Introduction</H1
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="QUICKSTART"
-></A
->1.1. Quickstart to Privoxy Development</H2
+NAME="QUICKSTART">1.1. Quickstart to Privoxy Development</H2
><P
-> The first step is to join the <A
+> You'll need an account on <A
+HREF="http://sourceforge.net/"
+TARGET="_top"
+>Sourceforge</A
+> to support our
+ development. Mail your ID to <A
HREF="mailto:developers@privoxy.org"
TARGET="_top"
->developer's mailing list</A
->.
- You can submit your ideas, or even better patches. Patches are best
- submitted to the Sourceforge tracker set up for this purpose, but
- can be sent to the list for review too.
- </P
-><P
-> You will also need to have a cvs package installed, which will
- entail having ssh installed as well (which seems to be a requirement of
- SourceForge), in order to access the cvs repository. Having the GNU build
- tools is also going to be important (particularly, autoconf and gmake).
+>the list</A
+> and wait until a
+ project manager has added you.
</P
><P
-> For the time being (read, this section is under construction), you can
- also refer to the extensive comments in the source code. In fact,
- reading the code is recommended in any case.
+> For the time being (read, this section is under construction), please
+ refer to the extensive comments in the source code.
</P
></DIV
></DIV
><H1
CLASS="SECT1"
><A
-NAME="NEWRELEASE"
-></A
->6. Releasing a New Version</H1
+NAME="NEWRELEASE">6. Releasing a New Version</H1
><P
> When we release versions of <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="VERSIONNUMBERS"
-></A
->6.1. Version numbers</H2
+NAME="VERSIONNUMBERS">6.1. Version numbers</H2
><P
> First you need to determine which version number the release will have.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> version numbers consist of three numbers,
- separated by dots, like in X.Y.Z (e.g. 3.0.0), where:
+ separated by dots, like in X.Y.Z, where:
<P
></P
><UL
This ensures that builds from CVS snapshots are easily distinguished from released versions.
The point version is reset to zero when the minor changes.
</P
-><P
-> Stable branches work a little differently, since there should be
- little to no development happening in such branches. Remember,
- only bugfixes, which presumably should have had some testing
- before being committed. Stable branches will then have their
- version reported as <TT
-CLASS="LITERAL"
->0.0.0</TT
->, during that period
- between releases when changes are being added. This is to denote
- that this code is <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not for release</I
-></SPAN
->. Then
- as the release nears, the version is bumped according: e.g.
- <TT
-CLASS="LITERAL"
->3.0.1 -> 0.0.0 -> 3.0.2</TT
->.
- </P
></LI
></UL
>
</P
-><P
-> In summary, the main CVS trunk is the development branch where new
- features are being worked on for the next stable series. This should
- almost always be where the most activity takes place. There is always at
- least one stable branch from the trunk, e.g now it is
- <TT
-CLASS="LITERAL"
->3.0</TT
->, which is only used to release stable versions.
- Once the initial *.0 release of the stable branch has been done, then as a
- rule, only bugfixes that have had prior testing should be committed to
- the stable branch. Once there are enough bugfixes to justify a new
- release, the version of this branch is again incremented Example: 3.0.0
- -> 3.0.1 -> 3.0.2, etc are all stable releases from within the stable
- branch. 3.1.x is currently the main trunk, and where work on 3.2.x is
- taking place. If any questions, please post to the devel list
- <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->before</I
-></SPAN
-> committing to a stable branch!
- </P
-><P
-> Developers should remember too that if they commit a bugfix to the stable
- branch, this will more than likely require a separate submission to the
- main trunk, since these are separate development trees within CVS. If you
- are working on both, then this would require at least two separate check
- outs (i.e main trunk, <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->and</I
-></SPAN
-> the stable release branch,
- which is <TT
-CLASS="LITERAL"
->v_3_0_branch</TT
-> at the moment).
- </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="BEFORERELEASE"
-></A
->6.2. Before the Release: Freeze</H2
+NAME="BEFORERELEASE">6.2. Before the Release: Freeze</H2
><P
> The following <SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="THERELEASE"
-></A
->6.3. Building and Releasing the Packages</H2
+NAME="THERELEASE">6.3. Building and Releasing the Packages</H2
><P
> Now the individual packages can be built and released. Note that for
GPL reasons the first package to be released is always the source tarball.
><H3
CLASS="SECT3"
><A
-NAME="PACK-GUIDELINES"
-></A
->6.3.1. Note on Privoxy Packaging</H3
+NAME="PACK-GUIDELINES">6.3.1. Note on Privoxy Packaging</H3
><P
> Please keep these general guidelines in mind when putting together
your package. These apply to <SPAN
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-TARBALL"
-></A
->6.3.2. Source Tarball</H3
+NAME="NEWRELEASE-TARBALL">6.3.2. Source Tarball</H3
><P
> First, <SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-RPM"
-></A
->6.3.3. SuSE, Conectiva or Red Hat RPM</H3
+NAME="NEWRELEASE-RPM">6.3.3. SuSE, Conectiva or Red Hat RPM</H3
><P
> In following text, replace <TT
CLASS="REPLACEABLE"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-OS2"
-></A
->6.3.4. OS/2</H3
+NAME="NEWRELEASE-OS2">6.3.4. OS/2</H3
><P
> First, <SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-SOLARIS"
-></A
->6.3.5. Solaris</H3
+NAME="NEWRELEASE-SOLARIS">6.3.5. Solaris</H3
><P
> Login to Sourceforge's compilefarm via ssh:
</P
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-WINDOWS"
-></A
->6.3.6. Windows</H3
+NAME="NEWRELEASE-WINDOWS">6.3.6. Windows</H3
><P
> You should ensure you have the latest version of Cygwin (from
<A
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-DEBIAN"
-></A
->6.3.7. Debian</H3
+NAME="NEWRELEASE-DEBIAN">6.3.7. Debian</H3
><P
> First, <SPAN
CLASS="emphasis"
><TD
><PRE
CLASS="PROGRAMLISTING"
-> debchange -v 3.0.1-stable-1 "New upstream version"</PRE
+> debchange -v 3.0.0-stable-1 "New upstream version"</PRE
></TD
></TR
></TABLE
> This will create
<TT
CLASS="FILENAME"
->../privoxy_3.0.1-stable-1_i386.deb</TT
+>../privoxy_3.0.0-stable-1_i386.deb</TT
>
which can be uploaded. To upload the package to Sourceforge, simply
issue
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-MACOSX"
-></A
->6.3.8. Mac OSX</H3
+NAME="NEWRELEASE-MACOSX">6.3.8. Mac OSX</H3
><P
> First, <SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-FREEBSD"
-></A
->6.3.9. FreeBSD</H3
+NAME="NEWRELEASE-FREEBSD">6.3.9. FreeBSD</H3
><P
> Login to Sourceforge's compile-farm via ssh:
</P
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-HPUX"
-></A
->6.3.10. HP-UX 11</H3
+NAME="NEWRELEASE-HPUX">6.3.10. HP-UX 11</H3
><P
> First, <SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-AMIGA"
-></A
->6.3.11. Amiga OS</H3
+NAME="NEWRELEASE-AMIGA">6.3.11. Amiga OS</H3
><P
> First, <SPAN
CLASS="emphasis"
><H3
CLASS="SECT3"
><A
-NAME="NEWRELEASE-AIX"
-></A
->6.3.12. AIX</H3
+NAME="NEWRELEASE-AIX">6.3.12. AIX</H3
><P
> Login to Sourceforge's compilefarm via ssh:
</P
><H2
CLASS="SECT2"
><A
-NAME="RELEASING"
-></A
->6.4. Uploading and Releasing Your Package</H2
+NAME="RELEASING">6.4. Uploading and Releasing Your Package</H2
><P
> After the package is ready, it is time to upload it
to SourceForge, and go through the release steps. The upload
CLASS="emphasis"
><I
CLASS="EMPHASIS"
->3.0.1
+>3.0.0
(beta)</I
></SPAN
>.
><H2
CLASS="SECT2"
><A
-NAME="AFTERRELEASE"
-></A
->6.5. After the Release</H2
+NAME="AFTERRELEASE">6.5. After the Release</H2
><P
> When all (or: most of the) packages have been uploaded and made available,
send an email to the <A
><H1
CLASS="SECT1"
><A
-NAME="SEEALSO"
-></A
->10. See also</H1
+NAME="SEEALSO">10. See also</H1
><P
> Other references and sites of interest to <SPAN
CLASS="APPLICATION"
><H1
CLASS="SECT1"
><A
-NAME="TESTING"
-></A
->5. Testing Guidelines</H1
+NAME="TESTING">5. Testing Guidelines</H1
><P
>To be filled.</P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="TESTING-PLAN"
-></A
->5.1. Testplan for releases</H2
+NAME="TESTING-PLAN">5.1. Testplan for releases</H2
><P
> Explain release numbers. major, minor. developer releases. etc.
><H2
CLASS="SECT2"
><A
-NAME="TESTING-REPORT"
-></A
->5.2. Test reports</H2
+NAME="TESTING-REPORT">5.2. Test reports</H2
><P
>Please submit test reports only with the <A
HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=395005"
><H1
CLASS="SECT1"
><A
-NAME="WEBSERVER-UPDATE"
-></A
->7. Update the Webserver</H1
+NAME="WEBSERVER-UPDATE">7. Update the Webserver</H1
><P
> The webserver should be updated at least with each stable release. When
updating, please follow these steps to make sure that no broken links,
><H1
CLASS="SECT1"
><A
-NAME="CONFIGURATION"
-></A
->3. Configuration</H1
+NAME="CONFIGURATION">3. Configuration</H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="GETUPDATES"
-></A
->3.1. Where can I get updated Actions Files?</H3
+NAME="GETUPDATES">3.1. Where can I get updated Actions Files?</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"
-></A
->3.2. Can I use my old config files?</H3
+NAME="NEWCONFIG">3.2. Can I use my old config files?</H3
><P
> The syntax, number, and purpose of configuration files has substantially
changed from <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN275"
-></A
->3.3. What is an <SPAN
+NAME="AEN266">3.3. What is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> file?</H3
site in one of your actions files, preferably in <TT
CLASS="FILENAME"
>user.action</TT
->.</P
+></P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="ACTIONSS"
-></A
->3.4. The <SPAN
+NAME="ACTIONSS">3.4. The <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> concept confuses me. Please list
><H3
CLASS="SECT2"
><A
-NAME="AEN294"
-></A
->3.5. How are actions files configured? What is the easiest
+NAME="AEN285">3.5. How are actions files configured? What is the easiest
way to do this?</H3
><P
> Actions files are just text files in a special syntax and can be edited
><H3
CLASS="SECT2"
><A
-NAME="AEN302"
-></A
->3.6. There are several different <SPAN
+NAME="AEN293">3.6. There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> files. What are
><H3
CLASS="SECT2"
><A
-NAME="YAHOO"
-></A
->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?</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"
-></A
->3.8. What's the difference between the
+NAME="CONFIGFILES">3.8. What's the difference between the
<SPAN
CLASS="QUOTE"
>"Cautious"</SPAN
>"Medium"</SPAN
> and <SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Advanced"</SPAN
> defaults?</H3
><P
> Configuring <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is not entirely trivial. To
- help you get started, we provide you with three different default action
- <SPAN
+> is not entirely trivial. To help you get
+ started, we provide you with three different default action <SPAN
CLASS="QUOTE"
->"profiles"</SPAN
-> in the web based actions file editor at <A
+>"packages"</SPAN
+> in
+ the web based actions file editor at <A
HREF="http://config.privoxy.org/show-status"
TARGET="_top"
>http://config.privoxy.org/show-status</A
>.
- See the <A
-HREF="../user-manual/actions-file.html"
-TARGET="_top"
-><I
-CLASS="CITETITLE"
->User
- Manual</I
-></A
-> for a list of actions, and how the default
- profiles are set.
+ The following table shows you, which of the most important features are enabled in each
+ configuration:
</P
><P
+><DIV
+CLASS="TABLE"
+><A
+NAME="AEN328"><P
+><B
+>Table 1. Default Configurations</B
+></P
+><TABLE
+BORDER="1"
+CLASS="CALSTABLE"
+><THEAD
+><TR
+><TH
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Feature</TH
+><TH
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Cautious</TH
+><TH
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Intermadiate</TH
+><TH
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Advanced</TH
+></TR
+></THEAD
+><TBODY
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Ad-blocking by URL</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Ad-filtering by size</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>GIF de-animation</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Referer forging</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Cookie handling</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>none</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>session-only</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>kill</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Pop-up killing</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Fast redirects</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>HTML taming</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>JavaScript taming</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Web-bug killing</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Fun text replacements</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Image tag reordering</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+><TR
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>Ad-filtering by link</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>no</TD
+><TD
+WIDTH="25%"
+ALIGN="LEFT"
+VALIGN="TOP"
+>yes</TD
+></TR
+></TBODY
+></TABLE
+></DIV
+></P
+><P
> Where the defaults are likely to break some sites, exceptions for
known popular <SPAN
CLASS="QUOTE"
>"problem"</SPAN
> sites are included, but in
- general, the more aggressive your default settings are, the more exceptions
- you will have to make later. See the <A
+ general, the more aggressive your default settings are, the more
+
exceptions you will have to make later. See the <A
HREF="../user-manual/index.html"
TARGET="_top"
-><I
-CLASS="CITETITLE"
->User Manual</I
-></A
->
- for a more deatiled discussion.</P
-><P
-> It should be noted that the <SPAN
-CLASS="QUOTE"
->"Radical"</SPAN
-> profile (formerly known
- as the <SPAN
-CLASS="QUOTE"
->"Advanced"</SPAN
-> profile) is not only more
- aggressive, but also includes fun and, extreme usage of most of
- <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> features. Use at your own risk!</P
+>user manual</A
+> for a more
+ deatiled discussion.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="BROWSECONFIG"
-></A
->3.9. Why can I change the configuration
+NAME="BROWSECONFIG">3.9. Why can I change the configuration
with a browser? Does that not raise security issues?</H3
><P
> It may seem strange that regular users can edit the config files with their
><H3
CLASS="SECT2"
><A
-NAME="AEN367"
-></A
->3.10. What is the <TT
+NAME="AEN431">3.10. What is the <TT
CLASS="FILENAME"
>default.filter</TT
> file? What is a <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN383"
-></A
->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
>. Configure
all browsers on the network then to use this address and port number.</P
><P
-> Alternately, you can have <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> listen on
- all available interfaces:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> listen-address :8118</PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> And then use <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
->
- <A
-HREF="../user-manual/config.html#PERMIT-ACCESS"
-TARGET="_top"
->permit-access</A
->
- feature to limit connections. A firewall in this situation is recommended
- as well.</P
-><P
-> The above steps should be the same for any TCP network, regardless of
- operating system.</P
-><P
> If you run <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN409"
-></A
->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.</H3
><P
> The replacement for blocked images can be controlled with the <A
HREF="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"
><H3
CLASS="SECT2"
><A
-NAME="AEN426"
-></A
->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?</H3
><P
> Remember that <A
HREF="general.html#WHATSANAD"
><H3
CLASS="SECT2"
><A
-NAME="AEN431"
-></A
->3.14. I see some images being replaced by a text
+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
><P
> This happens when the banners are not embedded in the HTML code of the
><H3
CLASS="SECT2"
><A
-NAME="SRVANY"
-></A
->3.15. Can <SPAN
+NAME="SRVANY">3.15. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a service
CLASS="COMMAND"
>srvany.exe</B
>.
- See the discussion at <A
+ The only catch is that this will effectively disable the
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> icon (and its menu!) in the taskbar. You can have
+ one or the other, but not both at this time :( </P
+><P
+> There is a pending feature request for this functionality. See the discussion
+ at <A
HREF="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118"
TARGET="_top"
>http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</A
->,
- for details, and a sample configuration.</P
-><P
-> Version 3.0.1 fixes the problem where the icon and menu where not available
- in the taskbar for this usage.</P
+>,
+ for details, and a sample configuration. </P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="OTHERPROXY"
-></A
->3.16. How can I make <SPAN
+NAME="OTHERPROXY">3.16. How can I make <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> work with other
><H3
CLASS="SECT2"
><A
-NAME="PORT-80"
-></A
->3.17. Can I just set <SPAN
+NAME="PORT-80">3.17. Can I just set <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> to use port 80
><H3
CLASS="SECT2"
><A
-NAME="TRANSPARENT"
-></A
->3.18. Can <SPAN
+NAME="TRANSPARENT">3.18. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a <SPAN
>http://www.transproxy.nlc.net.au/</A
>).</P
></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="OUTLOOK"
-></A
->3.19. How can I configure <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> for use with <SPAN
-CLASS="APPLICATION"
->Outlook
- Express</SPAN
->?</H3
-><P
-> <SPAN
-CLASS="APPLICATION"
->Outlook Express</SPAN
-> uses <SPAN
-CLASS="APPLICATION"
->Internet Explorer</SPAN
->
- components to both render HTML, and fetch any HTTP requests that may be embedded in an HTML email.
- So however you have <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> configured to work
- with IE, this configuration should automatically be shared.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="OUTLOOK-MORE"
-></A
->3.20. How can I have separate rules just for HTML mail?</H3
-><P
-> The short answer is, you can't. <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> has no way
- of knowing which particular application makes a request, so there is no way to
- distinguish between web pages and HTML mail.
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> just blindly proxies all requests. In the
- case of <SPAN
-CLASS="APPLICATION"
->Outlook Express</SPAN
-> (see above), OE uses
- IE anyway, and there is no way for <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> to ever
- be able to distinguish between them (nor could any other proxy type application for
- that matter).</P
-><P
-> For a good discussion of some of the issues involved (including privacy and
- security issues), see
- <A
-HREF="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118"
-TARGET="_top"
->http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</A
->.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="ALLOW-COOKIES"
-></A
->3.21. How can I allow permanent cookies for my trusted sites?</H3
-><P
-> There are several actions that relate to cookies. The default behavior is to
- allow only <SPAN
-CLASS="QUOTE"
->"session cookies"</SPAN
->, which means the cookies only last
- for the current browser session. This eliminates most kinds of abuse related
- to cookies. But there may be cases where we want cookies to last.</P
-><P
-> To disable all cookie actions, so that cookies are allowed unrestricted,
- both in and out, for <TT
-CLASS="LITERAL"
->example.com</TT
->: </P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
- .example.com</PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> Place the above in <TT
-CLASS="FILENAME"
->user.action</TT
->. Note some of these may
- be off by default anyway, so this might be redundant, but there is no harm
- being explicit in what you want to happen. <TT
-CLASS="FILENAME"
->user.action</TT
->
- includes an alias for this situation, called
- <TT
-CLASS="LITERAL"
->allow-cookies</TT
->.</P
-></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><H1
CLASS="SECT1"
><A
-NAME="CONTACT"
-></A
->6. Contacting the developers, Bug Reporting and Feature Requests</H1
+NAME="CONTACT">6. Contacting the developers, Bug Reporting and Feature Requests</H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT"
-></A
->6.1. Get Support</H2
+NAME="CONTACT-SUPPORT">6.1. Get Support</H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS"
-></A
->6.2. Report Bugs</H2
+NAME="CONTACT-BUGS">6.2. Report Bugs</H2
><P
> Please report all bugs <SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE"
-></A
->6.3. Request New Features</H2
+NAME="CONTACT-FEATURE">6.3. Request New Features</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"
-></A
->6.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS">6.4. Report Ads or Other Actions-Related Problems</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"
-></A
->6.5. Other</H2
+NAME="CONTACT-OTHER">6.5. Other</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!
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT"
-></A
->7. Privoxy Copyright, License and History</H1
+NAME="COPYRIGHT">7. Privoxy Copyright, License and History</H1
><P
> Copyright © 2001, 2002 by Privoxy Developers <TT
CLASS="EMAIL"
><H2
CLASS="SECT2"
><A
-NAME="AEN884"
-></A
->7.1. License</H2
+NAME="AEN891">7.1. License</H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN900"
-></A
->7.2. History</H2
+NAME="AEN907">7.2. History</H2
><P
> In the beginning, there was the
<A
><H1
CLASS="SECT1"
><A
-NAME="GENERAL"
-></A
->1. General Information</H1
+NAME="GENERAL">1. General Information</H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="NEWJB"
-></A
->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
><H3
CLASS="SECT2"
><A
-NAME="AEN45"
-></A
->1.2. Why <SPAN
+NAME="AEN45">1.2. Why <SPAN
CLASS="QUOTE"
>"Privoxy"</SPAN
>? Why a name change at all?</H3
><P
> The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make
- a name in their own right, especially now with the pending
- release of version 3.0.</P
+ a name in their own right.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="DIFFERS"
-></A
->1.3. How does <SPAN
+NAME="DIFFERS">1.3. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> differ
><H3
CLASS="SECT2"
><A
-NAME="PROXYMORON"
-></A
->1.4. What is a <SPAN
+NAME="PROXYMORON">1.4. What is a <SPAN
CLASS="QUOTE"
>"proxy"</SPAN
>? How does
><H3
CLASS="SECT2"
><A
-NAME="WHATSANAD"
-></A
->1.5. How does <SPAN
+NAME="WHATSANAD">1.5. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> know what is
><H3
CLASS="SECT2"
><A
-NAME="AEN136"
-></A
->1.6. Can <SPAN
+NAME="AEN136">1.6. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> make mistakes?
><H3
CLASS="SECT2"
><A
-NAME="BROWSERS2"
-></A
->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
><H3
CLASS="SECT2"
><A
-NAME="LICENSE"
-></A
->1.8. Is there is a license or fee? What about a
+NAME="LICENSE">1.8. Is there is a license or fee? What about a
warranty? Registration?</H3
><P
> <SPAN
><H3
CLASS="SECT2"
><A
-NAME="JOINTEAM"
-></A
->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?</H3
><DIV
CLASS="SECT3"
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-MONEY"
-></A
->1.9.1. Money Money Money</H4
+NAME="JOINTEAM-MONEY">1.9.1. Money Money Money</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"
-></A
->1.9.2. Software</H4
+NAME="JOINTEAM-SOFTWARE">1.9.2. Software</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"
-></A
->1.9.3. You want to work with us?</H4
+NAME="JOINTEAM-WORK">1.9.3. You want to work with us?</H4
><P
> Well, helping the team is always a good idea. We welcome new developers,
packaging gurus or documentation writers. Simply <A
><H1
CLASS="TITLE"
><A
-NAME="AEN2"
-></A
->Privoxy Frequently Asked Questions</H1
+NAME="AEN2">Privoxy Frequently Asked Questions</H1
><P
CLASS="PUBDATE"
> <SUB
><BR></P
><P
CLASS="PUBDATE"
->$Id: faq.sgml,v 1.61.2.27 2002/12/01 06:31:58 hal9 Exp $<BR></P
+>$Id: faq.sgml,v 1.61.2.18 2002/08/14 16:39:37 hal9 Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"
-></A
-><P
+NAME="AEN9"><P
></P
><P
> This FAQ gives quick answers to frequently asked questions about
> (tm).</P
><P
> Please note that this document is constantly evolving. This copy represents
- the state at the release of version 0.0.0.
+ the state at the release of version 3.0.0.
You can find the latest version of the document at <A
HREF="http://www.privoxy.org/faq/"
TARGET="_top"
></DT
><DT
>2.3. <A
-HREF="installation.html#EMAIL-CLIENT"
->Can I use <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> with my email client?</A
-></DT
-><DT
->2.4. <A
HREF="installation.html#NEWINSTALL"
>Can I install
<SPAN
>?</A
></DT
><DT
-HREF="installation.html#AEN218"
+HREF="installation.html#AEN209"
>I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
special I have to do now?</A
></DT
><DT
HREF="installation.html#LOCALHOST"
>What is the proxy address of <SPAN
CLASS="APPLICATION"
>?</A
></DT
><DT
HREF="installation.html#NOTHING"
>I just installed <SPAN
CLASS="APPLICATION"
></DT
><DT
>3.3. <A
-HREF="configuration.html#AEN275"
+HREF="configuration.html#AEN266"
>What is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
></DT
><DT
>3.5. <A
-HREF="configuration.html#AEN294"
+HREF="configuration.html#AEN285"
>How are actions files configured? What is the easiest
way to do this?</A
></DT
><DT
>3.6. <A
-HREF="configuration.html#AEN302"
+HREF="configuration.html#AEN293"
>There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
>"Medium"</SPAN
> and <SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Advanced"</SPAN
> defaults?</A
></DT
><DT
></DT
><DT
>3.10. <A
-HREF="configuration.html#AEN367"
+HREF="configuration.html#AEN431"
>What is the <TT
CLASS="FILENAME"
>default.filter</TT
></DT
><DT
>3.11. <A
-HREF="configuration.html#AEN383"
+HREF="configuration.html#AEN447"
>How can I set up <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>3.12. <A
-HREF="configuration.html#AEN409"
+HREF="configuration.html#AEN465"
>Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</A
></DT
><DT
>3.13. <A
-HREF="configuration.html#AEN426"
+HREF="configuration.html#AEN482"
>Why would anybody want to see a checkerboard pattern?</A
></DT
><DT
>3.14. <A
-HREF="configuration.html#AEN431"
+HREF="configuration.html#AEN487"
>I see some images being replaced by a text
instead of the checkerboard image. Why and how do I get rid of this?</A
></DT
>"transparent"</SPAN
> proxy?</A
></DT
-><DT
->3.19. <A
-HREF="configuration.html#OUTLOOK"
->How can I configure <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> for use with <SPAN
-CLASS="APPLICATION"
->Outlook
- Express</SPAN
->?</A
-></DT
-><DT
->3.20. <A
-HREF="configuration.html#OUTLOOK-MORE"
->How can I have separate rules just for HTML mail?</A
-></DT
-><DT
->3.21. <A
-HREF="configuration.html#ALLOW-COOKIES"
->How can I allow permanent cookies for my trusted sites?</A
-></DT
></DL
></DD
><DT
><DL
><DT
>4.1. <A
-HREF="misc.html#AEN500"
+HREF="misc.html#AEN528"
>How much does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.7. <A
-HREF="misc.html#AEN560"
+HREF="misc.html#AEN588"
>Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.8. <A
-HREF="misc.html#AEN571"
+HREF="misc.html#AEN599"
>Might some things break because header information or
content is being altered?</A
></DT
><DT
>4.9. <A
-HREF="misc.html#AEN582"
+HREF="misc.html#AEN610"
>Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.10. <A
-HREF="misc.html#AEN592"
+HREF="misc.html#AEN620"
>What about as a firewall? Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.11. <A
-HREF="misc.html#AEN598"
+HREF="misc.html#AEN626"
>I have large empty spaces / a checkerboard pattern now where
ads used to be. Why?</A
></DT
><DT
>4.12. <A
-HREF="misc.html#AEN603"
+HREF="misc.html#AEN631"
>How can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.13. <A
-HREF="misc.html#AEN618"
+HREF="misc.html#AEN642"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
and related issues?</A
></DT
-><DT
->4.19. <A
-HREF="misc.html#MICROSUCK"
->I've noticed that Privoxy changes <SPAN
-CLASS="QUOTE"
->"Microsoft"</SPAN
-> to
-<SPAN
-CLASS="QUOTE"
->"MicroSuck"</SPAN
->! Why are you manipulating my browsing?</A
-></DT
></DL
></DD
><DT
><DL
><DT
>5.1. <A
-HREF="trouble.html#AEN741"
+HREF="trouble.html#AEN755"
>I just upgraded and am getting <SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
></DT
><DT
>5.2. <A
-HREF="trouble.html#AEN754"
+HREF="trouble.html#AEN768"
>I just added a new rule, but the steenkin ad is
still getting through. How?</A
></DT
shows only: <SPAN
CLASS="MARKUP"
><html><body></body></html></SPAN
->. Without
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> the page loads fine.</A
-></DT
-><DT
->5.9. <A
-HREF="trouble.html#ERROR503"
->Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</A
+>.</A
></DT
></DL
></DD
><DL
><DT
>7.1. <A
-HREF="copyright.html#AEN884"
+HREF="copyright.html#AEN891"
>License</A
></DT
><DT
>7.2. <A
-HREF="copyright.html#AEN900"
+HREF="copyright.html#AEN907"
>History</A
></DT
></DL
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION"
-></A
->2. Installation</H1
+NAME="INSTALLATION">2. Installation</H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="WHICHBROWSERS"
-></A
->2.1. Which browsers are supported by <SPAN
+NAME="WHICHBROWSERS">2.1. Which browsers are supported by <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>?</H3
><H3
CLASS="SECT2"
><A
-NAME="WHICHOS"
-></A
->2.2. Which operating systems are supported?</H3
+NAME="WHICHOS">2.2. Which operating systems are supported?</H3
><P
> At present, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> is known to run on
- Windows(95, 98, ME, 2000, XP), Linux (RedHat, SuSE, Debian, Conectiva, Gentoo,
- Slackware), Mac OSX, OS/2, AmigaOS, BeOS, FreeBSD, NetBSD, OpenBSD, Solaris,
- and many more flavors of Unix.</P
+ Windows(95, 98, ME, 2000, XP), Linux (RedHat, SuSE, Debian, Conectiva, Gentoo),
+ Mac OSX, OS/2, AmigaOS, BeOS, FreeBSD, NetBSD, Solaris, and many more
+ flavors of Unix.</P
><P
> But any operating system that runs TCP/IP, can conceivably take advantage of
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="EMAIL-CLIENT"
-></A
->2.3. Can I use <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> with my email client?</H3
-><P
-> As long as there is some way to set a HTTP proxy for the client, then yes,
- any application can be used, whether it is strictly speaking a
- <SPAN
-CLASS="QUOTE"
->"browser"</SPAN
-> or not. Though this may not be the best approach for
- dealing with some of the common abuses of HTML in email. See <A
-HREF="configuration.html#OUTLOOK"
->How can I configure <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- with <SPAN
-CLASS="APPLICATION"
->Outlook Express</SPAN
->?</A
-> below for more on
- this. </P
-><P
-> Be aware that HTML email presents a number of unique security and privacy
- related issues, that can require advanced skills to overcome. The developers
- recommend using email clients that can be configured to convert HTML to plain
- text for these reasons.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="NEWINSTALL"
-></A
->2.4. Can I install
+NAME="NEWINSTALL">2.3. Can I install
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN218"
-></A
->2.5. I just installed <SPAN
+NAME="AEN209">2.4. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>. Is there anything
as a proxy by specifying the correct proxy address and port number
in the appropriate configuration area for the browser. See below.
You should also flush your browser's memory and disk cache to get rid of any
- cached junk items, and remove any stored cookies. </P
+ cached junk items. </P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="LOCALHOST"
-></A
->2.6. What is the proxy address of <SPAN
+NAME="LOCALHOST">2.5. What is the proxy address of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>?</H3
><H3
CLASS="SECT2"
><A
-NAME="NOTHING"
-></A
->2.7. I just installed <SPAN
+NAME="NOTHING">2.6. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, and nothing is happening.
><H1
CLASS="SECT1"
><A
-NAME="MISC"
-></A
->4. Miscellaneous</H1
+NAME="MISC">4. Miscellaneous</H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN500"
-></A
->4.1. How much does <SPAN
+NAME="AEN528">4.1. How much does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> slow my browsing down? This
><H3
CLASS="SECT2"
><A
-NAME="LOADINGTIMES"
-></A
->4.2. I noticed considerable
+NAME="LOADINGTIMES">4.2. I noticed considerable
delays in page requests compared to the old Junkbuster. What's wrong?</H3
><P
> If you use any <TT
><H3
CLASS="SECT2"
><A
-NAME="CONFIGURL"
-></A
->4.3. What are "http://config.privoxy.org/" and
+NAME="CONFIGURL">4.3. What are "http://config.privoxy.org/" and
"http://p.p/"?</H3
><P
> <A
>
takes you to a page saying <SPAN
CLASS="QUOTE"
->"This is Privoxy ..."</SPAN
+>"This is Privoxy.."</SPAN
>, everything is OK.
If you get a page saying <SPAN
CLASS="QUOTE"
>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 0.0.0.</P
+ upgrading to 3.0.0.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="BLOCKLIST"
-></A
->4.4. Do you still maintain the blocklists?</H3
+NAME="BLOCKLIST">4.4. Do you still maintain the blocklists?</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"
-></A
->4.5. How can I submit new ads?</H3
+NAME="NEWADS">4.5. How can I submit new ads?</H3
><P
>Yes, absolutely! Please see the <A
HREF="contact.html"
><H3
CLASS="SECT2"
><A
-NAME="IP"
-></A
->4.6. How can I hide my IP address?</H3
+NAME="IP">4.6. How can I hide my IP address?</H3
><P
> If you run both the browser and the proxy locally, you cannot hide your IP
address with <SPAN
HREF="http://anon.inf.tu-dresden.de/index_en.html"
TARGET="_top"
>http://anon.inf.tu-dresden.de/index_en.html</A
->).</P
+>.</P
><P
> There is, however, even in the single-machine case the possibility to make the
server believe that your machine is in fact a shared proxy serving a whole big
><H3
CLASS="SECT2"
><A
-NAME="AEN560"
-></A
->4.7. Can <SPAN
+NAME="AEN588">4.7. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> guarantee I am anonymous?</H3
><H3
CLASS="SECT2"
><A
-NAME="AEN571"
-></A
->4.8. Might some things break because header information or
+NAME="AEN599">4.8. Might some things break because header information or
content is being altered?</H3
><P
> Definitely. More and more sites use HTTP header content to decide what to
><H3
CLASS="SECT2"
><A
-NAME="AEN582"
-></A
->4.9. Can <SPAN
+NAME="AEN610">4.9. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> act as a <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN592"
-></A
->4.10. What about as a firewall? Can <SPAN
+NAME="AEN620">4.10. What about as a firewall? Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> protect me?</H3
><H3
CLASS="SECT2"
><A
-NAME="AEN598"
-></A
->4.11. I have large empty spaces / a checkerboard pattern now where
+NAME="AEN626">4.11. I have large empty spaces / a checkerboard pattern now where
ads used to be. Why?</H3
><P
> It would be technically possible eliminate the banners in a way that frees
><H3
CLASS="SECT2"
><A
-NAME="AEN603"
-></A
->4.12. How can <SPAN
+NAME="AEN631">4.12. How can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> filter Secure (HTTPS) URLs?</H3
CLASS="APPLICATION"
>Privoxy</SPAN
>'s ad blocking.</P
-><P
-> <SPAN
-CLASS="QUOTE"
->"Content cookies"</SPAN
-> (those that are embedded in the actual HTML or
- JS page content, see <TT
-CLASS="LITERAL"
-><A
-HREF="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES"
-TARGET="_top"
->filter{content-cookies}</A
-></TT
->),
- in an SSL transaction will be impossible to block under these conditions.
- Fortunately, this does not seem to be a very common scenario since most
- cookies come by traditional means.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN618"
-></A
->4.13. <SPAN
+NAME="AEN642">4.13. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> runs as a <SPAN
><H3
CLASS="SECT2"
><A
-NAME="TURNOFF"
-></A
->4.14. How can I temporarily disable <SPAN
+NAME="TURNOFF">4.14. How can I temporarily disable <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>?</H3
><H3
CLASS="SECT2"
><A
-NAME="REALLYOFF"
-></A
->4.15. When <SPAN
+NAME="REALLYOFF">4.15. When <SPAN
CLASS="QUOTE"
>"disabled"</SPAN
> is <SPAN
><H3
CLASS="SECT2"
><A
-NAME="CRUNCH"
-></A
->4.16. My logs show <SPAN
+NAME="CRUNCH">4.16. My logs show <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> <SPAN
><H3
CLASS="SECT2"
><A
-NAME="DOWNLOADS"
-></A
->4.17. Can <SPAN
+NAME="DOWNLOADS">4.17. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> effect files that I download
><H3
CLASS="SECT2"
><A
-NAME="SEEALSO"
-></A
->4.18. Where can I find more information about <SPAN
+NAME="SEEALSO">4.18. Where can I find more information about <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
></P
></P
></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="MICROSUCK"
-></A
->4.19. I've noticed that Privoxy changes <SPAN
-CLASS="QUOTE"
->"Microsoft"</SPAN
-> to
-<SPAN
-CLASS="QUOTE"
->"MicroSuck"</SPAN
->! Why are you manipulating my browsing?</H3
-><P
-> We're not. The text substitutions that you are seeing are disabled
- in the default configuration as shipped. You have either manually
- activated the <SPAN
-CLASS="QUOTE"
->"<TT
-CLASS="LITERAL"
->fun</TT
->"</SPAN
-> filter which
- is clearly labeled <SPAN
-CLASS="QUOTE"
->"Text replacements for subversive browsing
- fun!"</SPAN
-> or you have implicitly activated it by choosing the
- <SPAN
-CLASS="QUOTE"
->"Radical"</SPAN
-> profile in the web-based editor (formerly known
- as the <SPAN
-CLASS="APPLICATION"
->Advanced</SPAN
-> profile).</P
-></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><H1
CLASS="SECT1"
><A
-NAME="TROUBLE"
-></A
->5. Troubleshooting</H1
+NAME="TROUBLE">5. Troubleshooting</H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN741"
-></A
->5.1. I just upgraded and am getting <SPAN
+NAME="AEN755">5.1. I just upgraded and am getting <SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
>
><H3
CLASS="SECT2"
><A
-NAME="AEN754"
-></A
->5.2. I just added a new rule, but the steenkin ad is
+NAME="AEN768">5.2. I just added a new rule, but the steenkin ad is
still getting through. How?</H3
><P
> If the ad had been displayed before you added its URL, it will probably be
><H3
CLASS="SECT2"
><A
-NAME="BADSITE"
-></A
->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
>.
><H3
CLASS="SECT2"
><A
-NAME="DUN"
-></A
->5.4. After installing <SPAN
+NAME="DUN">5.4. After installing <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, I have to log in
><H3
CLASS="SECT2"
><A
-NAME="FTP"
-></A
->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
>
>
as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
</P
-><P
-> Most browsers understand FTP as well as HTTP. If you connect to a site, with
- a URL like <TT
-CLASS="LITERAL"
->ftp://ftp.example.com</TT
->, your browser is making
- an FTP connection, and not a HTTP connection. So while your browser may
- speak FTP, <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> does not, and cannot proxy
- such traffic.
- </P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="OSXIE"
-></A
->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
><H3
CLASS="SECT2"
><A
-NAME="OSXUNINSTALL"
-></A
->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
><P
><H3
CLASS="SECT2"
><A
-NAME="BLANKPAGE"
-></A
->5.8. I get a completely blank page at one site. <SPAN
+NAME="BLANKPAGE">5.8. I get a completely blank page at one site. <SPAN
CLASS="QUOTE"
>"View Source"</SPAN
>
shows only: <SPAN
CLASS="MARKUP"
><html><body></body></html></SPAN
->. Without
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> the page loads fine.</H3
+>.</H3
><P
-> Chances are that the site suffers from a bug in
- <A
-HREF="http://www.php.net/"
-TARGET="_top"
-><SPAN
+> This is often the result of a webserver using
+ <SPAN
CLASS="APPLICATION"
>PHP</SPAN
-></A
->,
- which results in empty pages being sent if the client explicitly requests
- an uncompressed page, like <SPAN
+> that mishandles the request
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> does.
- This bug has been fixed in PHP 4.2.3.
+> sends to not compress the content
+ (a <SPAN
+CLASS="APPLICATION"
+>PHP</SPAN
+> bug).
</P
><P
-> To find out if this is in fact the source of the problem, try adding
- the site to a <TT
-CLASS="LITERAL"
->-prevent-compression</TT
-> section in
- <TT
+> In a default configuration, <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> requests all
+ data be sent <SPAN
+CLASS="QUOTE"
+>"uncompressed"</SPAN
+>. This is required for the page
+ filtering and other magic to work. In some rare cases, the browser and
+ webserver miscommunicate and the result is a totally blank page. The
+ suggested work around is to selectively turn off this feature for sites
+ that exhibit such behavior. Example section for <TT
CLASS="FILENAME"
>user.action</TT
>:
></TD
></TR
></TABLE
-><P
-> If that works, you may also want to report the problem to the
- site's webmasters, telling them to use zlib.output_compression
- instead of ob_gzhandler in their PHP applications (workaround)
- or upgrade to PHP 4.2.3 or later (fix).
- </P
-></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="ERROR503"
-></A
->5.9. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</H3
-><P
-> More than likely this is a problem with the network stack. ZoneAlarm has
- been reported to cause this symptom -- even if not running. The solution is
- to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
- something better behaved in its place. Other firewall type products may
- cause similar type problems if not configured correctly.
- </P
></DIV
></DIV
><DIV
><H1
CLASS="TITLE"
><A
-NAME="AEN2"
-></A
->Privoxy - Home Page</H1
+NAME="AEN2">Privoxy - Home Page</H1
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN28"
-></A
-><P
+NAME="AEN28"><P
></P
><P
->
- </P
-><P
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
Junkbuster</SPAN
> (tm).</P
><P
-> The most recent release is 0.0.0 (UNRELEASED).
+> The most recent release is 3.0.0 (stable).
</P
><P
></P
><H3
CLASS="SECT1"
><A
-NAME="DOWNLOAD"
-></A
->Download</H3
+NAME="DOWNLOAD">Download</H3
><P
> <P
></P
><HR><H3
CLASS="SECT1"
><A
-NAME="DOCS"
-></A
->Documentation</H3
+NAME="DOCS">Documentation</H3
><P
> <P
></P
><HR><H3
CLASS="SECT1"
><A
-NAME="MOREINFO"
-></A
->More information</H3
+NAME="MOREINFO">More information</H3
><P
> <P
></P
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN94"
-></A
-></H2
+NAME="AEN92"></H2
><P
><DIV
CLASS="INFORMALTABLE"
><A
-NAME="AEN97"
-></A
-><P
+NAME="AEN95"><P
></P
><TABLE
BORDER="0"
<HTML><HEAD><TITLE>Manpage of PRIVOXY</TITLE>
<LINK REL="STYLESHEET" TYPE="text/css" HREF="../p_doc.css"></HEAD><BODY>
<H1>PRIVOXY</H1>
-Section: (1)<BR>Updated:
18 March 2003<BR><A HREF="#index">Index</A>
+Section: (1)<BR>Updated:
26 August 2002<BR><A HREF="#index">Index</A>
<HR>
<A NAME="lbAB"> </A>
<I>group</I> was not given, the default group of
<I>user</I>. Exit if the privileges are not
sufficient to do so.
-<DT><B>--chroot</B><DD>
-Before changing to the user ID given in the --user option, chroot to
-that user's home directory, i.e. make the kernel pretend to the
-<B>Privoxy</B> process that the directory tree starts
-there. If set up carefully, this can limit the impact of possible
-vulnerabilities in <B>Privoxy</B> to the files contained in
-that hierarchy.
</DL>
<P>
Stefan Waldherr
Thomas Steudten
Rodney Stromlund
- Johny Agotnes
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
Hal Burgiss (docs)
- Mattes Dolak
Karsten Hopp (Red Hat)
Alexander Lazic
- Daniel Leite
Gábor Lipták
- Andrew Lock (Win32)
- Guy Laroche
+ Guy
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
David Schmidt (OS/2, Mac OSX ports)
Joerg Strohmayer (Amiga)
- Sviatoslav Sviridov
Sarantis Paskalis
</PRE>
This document was created by
man2html,
using the manual pages.<BR>
-Time: 00:37:30 GMT, March 19, 2003
+Time: 16:17:37 GMT, August 26, 2002
</BODY>
</HTML>
><H1
CLASS="TITLE"
><A
-NAME="AEN2"
-></A
->Privoxy - The Privacy Enhancing Proxy</H1
+NAME="AEN2">Privoxy - The Privacy Enhancing Proxy</H1
><H2
CLASS="SUBTITLE"
->Project Index Page v0.0.0</H2
+>Project Index Page v3.0.0</H2
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN29"
-></A
-><P
+NAME="AEN29"><P
></P
><P
->
- </P
-><P
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><H3
CLASS="SECT1"
><A
-NAME="DOWNLOAD"
-></A
->Download</H3
+NAME="DOWNLOAD">Download</H3
><P
> <P
></P
><HR><H3
CLASS="SECT1"
><A
-NAME="DOCS"
-></A
->Documentation</H3
+NAME="DOCS">Documentation</H3
><P
> <P
></P
><HR><H3
CLASS="SECT1"
><A
-NAME="MOREINFO"
-></A
->More information</H3
+NAME="MOREINFO">More information</H3
><P
> <P
></P
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN91"
-></A
-></H2
+NAME="AEN89"></H2
><P
> <SUB
> Copyright © 2001, 2002 by Privoxy Developers
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Main Configuration File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="ACTIONS-FILE"
-></A
->8. Actions Files</H1
+NAME="ACTIONS-FILE">8. Actions Files</H1
><P
> The actions files are used to define what actions
<SPAN
are three such files included with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
- with differing purposes:
+> (as of
+ version 2.9.15), with differing purposes:
</P
><P
> <P
>. It is not recommend
to edit this file.
</P
-><P
-> The default profiles, and their associated actions, as pre-defined in
- <TT
-CLASS="FILENAME"
->standard.action</TT
-> are:
- </P
-><P
-> <DIV
-CLASS="TABLE"
-><A
-NAME="AEN1719"
-></A
-><P
-><B
->Table 1. Default Configurations</B
-></P
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><THEAD
-><TR
-><TH
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Feature</TH
-><TH
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Cautious</TH
-><TH
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Medium</TH
-><TH
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Adventuresome</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Ad-blocking by URL</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Ad-filtering by size</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->GIF de-animation</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Referer forging</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Cookie handling</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->none</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->session-only</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->kill</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Pop-up killing</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->unsolicited</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->unsolicited</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->all</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Fast redirects</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->HTML taming</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->JavaScript taming</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Web-bug killing</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Fun text replacements</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Image tag reordering</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Ad-filtering by link</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-><TR
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->Demoronizer</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->no</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-><TD
-WIDTH="25%"
-ALIGN="LEFT"
-VALIGN="TOP"
->yes</TD
-></TR
-></TBODY
-></TABLE
-></DIV
->
- </P
></LI
></UL
>
</P
><P
> The list of actions files to be used are defined in the main configuration
- file, and are processed in the order they are defined (e.g.
- <TT
-CLASS="FILENAME"
->default.action</TT
-> is typically process before
- <TT
-CLASS="FILENAME"
->user.action</TT
->). The content of these can all be viewed and
- edited from <A
+ file, and are processed in the order they are defined. The content of these
+ can all be viewed and edited from <A
HREF="http://config.privoxy.org/show-status"
TARGET="_top"
>http://config.privoxy.org/show-status</A
><H2
CLASS="SECT2"
><A
-NAME="AEN1818"
-></A
->8.1. Finding the Right Mix</H2
+NAME="AEN1640">8.1. Finding the Right Mix</H2
><P
> Note that some <A
HREF="actions-file.html#ACTIONS"
CLASS="QUOTE"
>"trusted"</SPAN
> sites you
- will have to make later. If, for example, you want to crunch all cookies per
+ will have to make later. If, for example, you want to kill popup windows per
default, you'll have to make exceptions from that rule for sites that you
- regularly use and that require cookies for actually useful puposes, like maybe
- your bank, favorite shop, or newspaper. </P
+ regularly use and that require popups for actually useful content, like maybe
+ your bank, favorite shop, or newspaper.</P
><P
> We have tried to provide you with reasonable rules to start from in the
distribution actions files. But there is no general rule of thumb on these
><H2
CLASS="SECT2"
><A
-NAME="AEN1825"
-></A
->8.2. How to Edit</H2
+NAME="AEN1647">8.2. How to Edit</H2
><P
> The easiest way to edit the actions files is with a browser by
using our browser-based editor, which can be reached from <A
>"Medium"</SPAN
> or <SPAN
CLASS="QUOTE"
->"Adventuresome"</SPAN
->.
- Warning: the <SPAN
-CLASS="QUOTE"
->"Adventuresome"</SPAN
-> setting is not only more aggressive,
- but includes settings that are fun and subversive, and which some may find of
- dubious merit!</P
+>"Advanced"</SPAN
+>.</P
><P
> If you prefer plain text editing to GUIs, you can of course also directly edit the
the actions files. Look at <TT
><H2
CLASS="SECT2"
><A
-NAME="ACTIONS-APPLY"
-></A
->8.3. How Actions are Applied to URLs</H2
+NAME="ACTIONS-APPLY">8.3. How Actions are Applied to URLs</H2
><P
> Actions files are divided into sections. There are special sections,
like the <SPAN
><H2
CLASS="SECT2"
><A
-NAME="AF-PATTERNS"
-></A
->8.4. Patterns</H2
-><P
->
- As mentioned, <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> uses <SPAN
-CLASS="QUOTE"
->"patterns"</SPAN
->
- to determine what actions might apply to which sites and pages your browser
- attempts to access. These <SPAN
-CLASS="QUOTE"
->"patterns"</SPAN
-> use wild card type
- <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->pattern</I
-></SPAN
-> matching to achieve a high degree of
- flexibility. This allows one expression to be expanded and potentially match
- against many similar patterns.</P
+NAME="AF-PATTERNS">8.4. Patterns</H2
><P
-> Generally, a <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> pattern has the form
- <TT
+> Generally, a pattern has the form <TT
CLASS="LITERAL"
><domain>/<path></TT
->, where both the
- <TT
+>,
+ where both the <TT
CLASS="LITERAL"
><domain></TT
> and <TT
CLASS="LITERAL"
><path></TT
-> are
- optional. (This is why the special <TT
+>
+ are optional. (This is why the pattern <TT
CLASS="LITERAL"
>/</TT
-> pattern matches all
- URLs). Note that the protocol portion of the URL pattern (e.g.
- <TT
-CLASS="LITERAL"
->http://</TT
->) should <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not</I
-></SPAN
-> be included in
- the pattern. This is assumed already!</P
+> matches all URLs).</P
><P
></P
><DIV
><H3
CLASS="SECT3"
><A
-NAME="AEN1898"
-></A
->8.4.1. The Domain Pattern</H3
+NAME="AEN1711">8.4.1. The Domain Pattern</H3
><P
> The matching of the domain part offers some flexible options: if the
domain starts or ends with a dot, it becomes unanchored at that end.
><H3
CLASS="SECT3"
><A
-NAME="AEN1960"
-></A
->8.4.2. The Path Pattern</H3
+NAME="AEN1773">8.4.2. The Path Pattern</H3
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="ACTIONS"
-></A
->8.5. Actions</H2
+NAME="ACTIONS">8.5. Actions</H2
><P
> All actions are disabled by default, until they are explicitly enabled
somewhere in an actions file. Actions are turned on if preceded with a
><H4
CLASS="SECT3"
><A
-NAME="ADD-HEADER"
-></A
->8.5.1. add-header</H4
+NAME="ADD-HEADER">8.5.1. add-header</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="BLOCK"
-></A
->8.5.2. block</H4
+NAME="BLOCK">8.5.2. block</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="CRUNCH-INCOMING-COOKIES"
-></A
->8.5.3. crunch-incoming-cookies</H4
+NAME="CRUNCH-INCOMING-COOKIES">8.5.3. crunch-incoming-cookies</H4
><P
></P
><DIV
>session-cookies-only</A
></TT
> action,
- since it would prevent the session cookies from being set. See also
- <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER-CONTENT-COOKIES"
->filter-content-cookies</A
-></TT
->.
+ since it would prevent the session cookies from being set.
</P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="CRUNCH-OUTGOING-COOKIES"
-></A
->8.5.4. crunch-outgoing-cookies</H4
+NAME="CRUNCH-OUTGOING-COOKIES">8.5.4. crunch-outgoing-cookies</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="DEANIMATE-GIFS"
-></A
->8.5.5. deanimate-gifs</H4
+NAME="DEANIMATE-GIFS">8.5.5. deanimate-gifs</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="DOWNGRADE-HTTP-VERSION"
-></A
->8.5.6. downgrade-http-version</H4
+NAME="DOWNGRADE-HTTP-VERSION">8.5.6. downgrade-http-version</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="FAST-REDIRECTS"
-></A
->8.5.7. fast-redirects</H4
+NAME="FAST-REDIRECTS">8.5.7. fast-redirects</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="FILTER"
-></A
->8.5.8. filter</H4
+NAME="FILTER">8.5.8. filter</H4
><P
></P
><DIV
>config file</A
>. The
default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered
- data, and all pending data, is passed through unfiltered.
- </P
-><P
-> Inappropriate MIME types, such as zipped files, are not filtered at all.
- Encrypted SSL data (from HTTPS servers) cannot be filtered either since
- this would violate the integrity of the secure transaction.
+ data, and all pending data, is passed through unfiltered. Inappropriate
+ MIME types are not filtered.
</P
><P
> At this time, <SPAN
><DD
><P
> <A
-NAME="FILTER-JS-ANNOYANCES"
+NAME="FILTER-HTML-ANNOYANCES"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</PRE
+>+filter{html-annoyances} # Get rid of particularly annoying HTML abuse.</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-JS-EVENTS"
+NAME="FILTER-JS-ANNOYANCES"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)</PRE
+>+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-HTML-ANNOYANCES"
+NAME="FILTER-BANNERS-BY-SIZE"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{html-annoyances} # Get rid of particularly annoying HTML abuse</PRE
+>+filter{banners-by-size} # Kill banners based on their size for this page (<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>very</I
+></SPAN
+> efficient!)</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-CONTENT-COOKIES"
+NAME="FILTER-BANNERS-BY-LINK"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{content-cookies} # Kill cookies that come in the HTML or JS content</PRE
+>+filter{banners-by-link} # Kill banners based on the link they are contained in (experimental)</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-REFRESH-TAGS"
+NAME="FILTER-IMG-REORDER"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</PRE
+>+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-UNSOLICITED-POPUPS"
+NAME="FILTER-CONTENT-COOKIES"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{unsolicited-popups} # Disable only unsolicited pop-up windows</PRE
+>+filter{content-cookies} # Kill cookies that come sneaking in the HTML or JS content</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-ALL-POPUPS"
+NAME="FILTER-POPUPS"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{all-popups} # Kill all popups in JavaScript and HTML</PRE
+>+filter{popups} # Kill all popups in JS and HTML</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-IMG-REORDER"
+NAME="FILTER-WEBBUGS"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective</PRE
+>+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-BANNERS-BY-SIZE"
+NAME="FILTER-FUN"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{banners-by-size} # Kill banners by size</PRE
+>+filter{fun} # Text replacements for subversive browsing fun!</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-BANNERS-BY-LINK"
+NAME="FILTER-FRAMESET-BORDERS"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{banners-by-link} # Kill banners by their links to known clicktrackers</PRE
+>+filter{frameset-borders} # Give frames a border and make them resizeable</PRE
></TD
></TR
></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-WEBBUGS"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-TINY-TEXTFORMS"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-JUMPING-WINDOWS"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{jumping-windows} # Prevent windows from resizing and moving themselves</PRE
-></TD
-></TR
-></TABLE
->
+>
</P
><P
> <A
-NAME="FILTER-FRAMESET-BORDERS"
+NAME="FILTER-REFRESH-TAGS"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{frameset-borders} # Give frames a border and make them resizable</PRE
+>+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-DEMORONIZER"
+NAME="FILTER-NIMDA"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{demoronizer} # Fix MS's non-standard use of standard charsets</PRE
+>+filter{nimda} # Remove Nimda (virus) code.</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-QUICKTIME-KIOSKMODE"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{quicktime-kioskmode} # Make Quicktime movies saveable</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-FUN"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{fun} # Text replacements for subversive browsing fun!</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
NAME="FILTER-CRUDE-PARENTAL"
></A
>
><TD
><PRE
CLASS="SCREEN"
->+filter{crude-parental} # Crude parental filtering (demo only)</PRE
+>+filter{crude-parental} # Kill all web pages that contain the words "sex" or "warez"</PRE
></TD
></TR
></TABLE
</P
><P
> <A
-NAME="FILTER-IE-EXPLOITS"
+NAME="FILTER-JS-EVENTS"
></A
>
<TABLE
><TD
><PRE
CLASS="SCREEN"
->+filter{ie-exploits} # Disable some known Internet Explorer bug exploits</PRE
+>+filter{js-events} # Kill all JS event bindings (<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Radically destructive!</I
+></SPAN
+> Only for extra nasty sites) </PRE
></TD
></TR
></TABLE
><H4
CLASS="SECT3"
><A
-NAME="HANDLE-AS-IMAGE"
-></A
->8.5.9. handle-as-image</H4
+NAME="HANDLE-AS-IMAGE">8.5.9. handle-as-image</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="HIDE-FORWARDED-FOR-HEADERS"
-></A
->8.5.10. hide-forwarded-for-headers</H4
+NAME="HIDE-FORWARDED-FOR-HEADERS">8.5.10. hide-forwarded-for-headers</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="HIDE-FROM-HEADER"
-></A
->8.5.11. hide-from-header</H4
+NAME="HIDE-FROM-HEADER">8.5.11. hide-from-header</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="HIDE-REFERRER"
-></A
->8.5.12. hide-referrer</H4
+NAME="HIDE-REFERRER">8.5.12. hide-referrer</H4
><A
NAME="HIDE-REFERER"
></A
><H4
CLASS="SECT3"
><A
-NAME="HIDE-USER-AGENT"
-></A
->8.5.13. hide-user-agent</H4
+NAME="HIDE-USER-AGENT">8.5.13. hide-user-agent</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="KILL-POPUPS"
-></A
->8.5.14. kill-popups<A
+NAME="KILL-POPUPS">8.5.14. kill-popups<A
NAME="KILL-POPUP"
></A
></H4
>Typical use:</DT
><DD
><P
->Eliminate those annoying pop-up windows (deprecated)</P
+>Eliminate those annoying pop-up windows</P
></DD
><DT
>Effect:</DT
>Notes:</DT
><DD
><P
-> This action is basically a built-in, hardwired special-purpose filter
+> This action is easily confused with the built-in, hardwired <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#FILTER"
+>filter</A
+></TT
+>
action, but there are important differences: For <TT
CLASS="LITERAL"
>kill-popups</TT
<TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#FILTER-ALL-POPUPS"
->filter{<TT
-CLASS="REPLACEABLE"
-><I
->all-popups</I
-></TT
->}</A
-></TT
->
- does and is not as smart as <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
->filter{<TT
+HREF="actions-file.html#FILTER"
+>filter</A
+>{<TT
CLASS="REPLACEABLE"
><I
->unsolicited-popups</I
+>popups</I
></TT
->}</A
+>}</TT
>
- </TT
->is.
+ does.
</P
><P
> Think of it as a fast and efficient replacement for a filter that you
> action over its filter equivalent.
</P
><P
-> Killing all pop-ups unconditionally is problematic. Many shops and banks rely on
- pop-ups to display forms, shopping carts etc, and the <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
->filter{<TT
-CLASS="REPLACEABLE"
-><I
->unsolicited-popups</I
-></TT
->}</A
->
- </TT
-> does a fairly good job of catching only the unwanted ones.
- </P
-><P
-> If the only kind of pop-ups that you want to kill are exit consoles (those
+> Killing all pop-ups is a dangerous business. Many shops and banks rely on
+ pop-ups to display forms, shopping carts etc, and killing only the unwanted pop-ups
+ would require artificial intelligence in <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>.
+ If the only kind of pop-ups that you want to kill are exit consoles (those
<SPAN
CLASS="emphasis"
><I
><H4
CLASS="SECT3"
><A
-NAME="LIMIT-CONNECT"
-></A
->8.5.15. limit-connect</H4
+NAME="LIMIT-CONNECT">8.5.15. limit-connect</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="PREVENT-COMPRESSION"
-></A
->8.5.16. prevent-compression</H4
+NAME="PREVENT-COMPRESSION">8.5.16. prevent-compression</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SEND-VANILLA-WAFER"
-></A
->8.5.17. send-vanilla-wafer</H4
+NAME="SEND-VANILLA-WAFER">8.5.17. send-vanilla-wafer</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SEND-WAFER"
-></A
->8.5.18. send-wafer</H4
+NAME="SEND-WAFER">8.5.18. send-wafer</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SESSION-COOKIES-ONLY"
-></A
->8.5.19. session-cookies-only</H4
+NAME="SESSION-COOKIES-ONLY">8.5.19. session-cookies-only</H4
><P
></P
><DIV
> Allow only temporary <SPAN
CLASS="QUOTE"
>"session"</SPAN
-> cookies (for the current
- browser session <SPAN
+> cookies (for the current browser session <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>only</I
></SPAN
->).
+>).
</P
></DD
><DT
> field from <SPAN
CLASS="QUOTE"
>"Set-Cookie:"</SPAN
->
- server headers. Most browsers will not store such cookies permanently and
- forget them in between sessions.
+> server headers.
+ Most browsers will not store such cookies permanently and forget them in between sessions.
</P
></DD
><DT
>
field. If you use an exotic browser, you might want to try it out to be sure.
</P
-><P
-> This setting also has no effect on cookies that may have been stored
- previously by the browser before starting <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->.
- These would have to be removed manually.
- </P
-><P
-> <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> also uses
- the <A
-HREF="actions-file.html#FILTER-CONTENT-COOKIES"
->content-cookies filter</A
->
- to block some types of cookies. Content cookies are not effected by
- <TT
-CLASS="LITERAL"
->session-cookies-only</TT
->.
- </P
></DD
><DT
>Example usage:</DT
><H4
CLASS="SECT3"
><A
-NAME="SET-IMAGE-BLOCKER"
-></A
->8.5.20. set-image-blocker</H4
+NAME="SET-IMAGE-BLOCKER">8.5.20. set-image-blocker</H4
><P
></P
><DIV
><H3
CLASS="SECT3"
><A
-NAME="AEN2914"
-></A
->8.5.21. Summary</H3
+NAME="AEN2701">8.5.21. Summary</H3
><P
> Note that many of these actions have the potential to cause a page to
misbehave, possibly even not to display at all. There are many ways
><H2
CLASS="SECT2"
><A
-NAME="ALIASES"
-></A
->8.6. Aliases</H2
+NAME="ALIASES">8.6. Aliases</H2
><P
> Custom <SPAN
CLASS="QUOTE"
# These aliases just save typing later:
# (Note that some already use other aliases!)
#
- +crunch-all-cookies = +<A
-HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
->crunch-incoming-cookies</A
-> +<A
-HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
->crunch-outgoing-cookies</A
->
- -crunch-all-cookies = -<A
-HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
->crunch-incoming-cookies</A
-> -<A
-HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
->crunch-outgoing-cookies</A
->
+ +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
+ -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
block-as-image = +block +handle-as-image
- mercy-for-cookies = -crunch-all-cookies -<A
-HREF="actions-file.html#SESSION-COOKIES-ONLY"
->session-cookies-only</A
-> -<A
-HREF="actions-file.html#FILTER-CONTENT-COOKIES"
->filter{content-cookies}</A
->
+ mercy-for-cookies = -crunch-all-cookies -session-cookies-only
# These aliases define combinations of actions
# that are useful for certain types of sites:
#
- fragile = -<A
-HREF="actions-file.html#BLOCK"
->block</A
-> -<A
-HREF="actions-file.html#FILTER"
->filter</A
-> -crunch-all-cookies -<A
-HREF="actions-file.html#FAST-REDIRECTS"
->fast-redirects</A
-> -<A
-HREF="actions-file.html#HIDE-REFERER"
->hide-referrer</A
-> -<A
-HREF="actions-file.html#KILL-POPUPS"
->kill-popups</A
->
- shop = -crunch-all-cookies -<A
-HREF="actions-file.html#FILTER-ALL-POPUPS"
->filter{all-popups}</A
-> -<A
-HREF="actions-file.html#KILL-POPUPS"
->kill-popups</A
->
+ fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
+ shop = -crunch-all-cookies -filter{popups} -kill-popups
# Short names for other aliases, for really lazy people ;-)
#
# These shops require pop-ups:
#
- {shop -kill-popups -filter{all-popups}}
+ {shop -kill-popups -filter{popups}}
.dabs.com
.overclockers.co.uk</PRE
></TD
><H2
CLASS="SECT2"
><A
-NAME="ACT-EXAMPLES"
-></A
->8.7. Actions Files Tutorial</H2
+NAME="ACT-EXAMPLES">8.7. Actions Files Tutorial</H2
><P
> The above chapters have shown <A
HREF="actions-file.html"
><H3
CLASS="SECT3"
><A
-NAME="AEN2979"
-></A
->8.7.1. default.action</H3
+NAME="AEN2753">8.7.1. default.action</H3
><P
>Every config file should start with a short comment stating its purpose:</P
><P
##########################################################################
{{alias}}
- # These aliases just save typing later:
- # (Note that some already use other aliases!)
- #
- +crunch-all-cookies = +<A
-HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
->crunch-incoming-cookies</A
-> +<A
-HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
->crunch-outgoing-cookies</A
->
- -crunch-all-cookies = -<A
-HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
->crunch-incoming-cookies</A
-> -<A
-HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
->crunch-outgoing-cookies</A
->
- block-as-image = +block +handle-as-image
- mercy-for-cookies = -crunch-all-cookies -<A
-HREF="actions-file.html#SESSION-COOKIES-ONLY"
->session-cookies-only</A
-> -<A
-HREF="actions-file.html#FILTER-CONTENT-COOKIES"
->filter{content-cookies}</A
->
+# These aliases just save typing later:
+# (Note that some already use other aliases!)
+#
++crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
+-crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
+block-as-image = +block +handle-as-image
+mercy-for-cookies = -crunch-all-cookies -session-cookies-only
- # These aliases define combinations of actions
- # that are useful for certain types of sites:
- #
- fragile = -<A
-HREF="actions-file.html#BLOCK"
->block</A
-> -<A
-HREF="actions-file.html#FILTER"
->filter</A
-> -crunch-all-cookies -<A
-HREF="actions-file.html#FAST-REDIRECTS"
->fast-redirects</A
-> -<A
-HREF="actions-file.html#HIDE-REFERER"
->hide-referrer</A
-> -<A
-HREF="actions-file.html#KILL-POPUPS"
->kill-popups</A
->
- shop = -crunch-all-cookies -<A
-HREF="actions-file.html#FILTER-ALL-POPUPS"
->filter{all-popups}</A
-> -<A
-HREF="actions-file.html#KILL-POPUPS"
->kill-popups</A
-></PRE
+# These aliases define combinations of actions
+# that are useful for certain types of sites:
+#
+fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
+shop = mercy-for-cookies -filter{popups} -kill-popups</PRE
></TD
></TR
></TABLE
+<A
HREF="actions-file.html#FAST-REDIRECTS"
>fast-redirects</A
-> \
- +<A
-HREF="actions-file.html#FILTER-JS-ANNOYANCES"
->filter{js-annoyances}</A
-> \
- -<A
-HREF="actions-file.html#FILTER-JS-EVENTS"
->filter{js-events}</A
> \
+<A
HREF="actions-file.html#FILTER-HTML-ANNOYANCES"
>filter{html-annoyances}</A
+> \
+ +<A
+HREF="actions-file.html#FILTER-JS-ANNOYANCES"
+>filter{js-annoyances}</A
> \
-<A
HREF="actions-file.html#FILTER-CONTENT-COOKIES"
>filter{content-cookies}</A
> \
+<A
-HREF="actions-file.html#FILTER-REFRESH-TAGS"
->filter{refresh-tags}</A
+HREF="actions-file.html#FILTER-POPUPS"
+>filter{popups}</A
> \
+<A
-HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
->filter{unsolicited-popups}</A
+HREF="actions-file.html#FILTER-WEBBUGS"
+>filter{webbugs}</A
> \
-<A
-HREF="actions-file.html#FILTER-ALL-POPUPS"
->filter{all-popups}</A
+HREF="actions-file.html#FILTER-REFRESH-TAGS"
+>filter{refresh-tags}</A
+> \
+ -<A
+HREF="actions-file.html#FILTER-FUN"
+>filter{fun}</A
> \
+<A
-HREF="actions-file.html#FILTER-IMG-REORDER"
->filter{img-reorder}</A
+HREF="actions-file.html#FILTER-NIMDA"
+>filter{nimda}</A
> \
+<A
HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
-<A
HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
>filter{banners-by-link}</A
-> \
- +<A
-HREF="actions-file.html#FILTER-WEBBUGS"
->filter{webbugs}</A
> \
-<A
-HREF="actions-file.html#FILTER-TINY-TEXTFORMS"
->filter{tiny-textforms}</A
-> \
- +<A
-HREF="actions-file.html#FILTER-JUMPING-WINDOWS"
->filter{jumping-windows}</A
-> \
- -<A
-HREF="actions-file.html#FILTER-FRAMESET-BORDERS"
->filter{frameset-borders}</A
-> \
- +<A
-HREF="actions-file.html#FILTER-DEMORONIZER"
->filter{demoronizer}</A
+HREF="actions-file.html#FILTER-IMG-REORDER"
+>filter{img-reorder}</A
> \
-<A
HREF="actions-file.html#FILTER-SHOCKWAVE-FLASH"
>filter{shockwave-flash}</A
-> \
- -<A
-HREF="actions-file.html#FILTER-QUICKTIME-KIOSKMODE"
->filter{quicktime-kioskmode}</A
-> \
- -<A
-HREF="actions-file.html#FILTER-FUN"
->filter{fun}</A
> \
-<A
HREF="actions-file.html#FILTER-CRUDE-PARENTAL"
>filter{crude-parental}</A
> \
-HREF="actions-file.html#FILTER-IE-EXPLOITS"
->filter{ie-exploits}</A
-> \
+HREF="actions-file.html#FILTER-JS-EVENTS"
+>filter{js-events}</A
+> \
-<A
HREF="actions-file.html#HANDLE-AS-IMAGE"
>handle-as-image</A
></SPAN
> the
default!) need exceptions, i.e. we need to specify explicitly what we
- want to block in later sections.</P
+ want to block in later sections.
+ We will also want to make exceptions from our general pop-up-killing,
+ and use our defined aliases for that.</P
><P
> The first of our specialized sections is concerned with <SPAN
CLASS="QUOTE"
></TABLE
></P
><P
+> Then, there are sites which rely on pop-up windows (yuck!) to work.
+ Since we made pop-up-killing our default above, we need to make exceptions
+ now. <A
+HREF="http://www.mozilla.org/"
+TARGET="_top"
+>Mozilla</A
+> users, who
+ can turn on smart handling of unwanted pop-ups in their browsers, can
+ safely choose
+ -<TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#FILTER-POPUPS"
+>filter{popups}</A
+></TT
+> (and
+ -<TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#KILL-POPUPS"
+>kill-popups</A
+></TT
+>) above
+ and hence don't need this section. Anyway, disabling an already disabled
+ action doesn't hurt, so we'll define our exceptions regardless of what was
+ chosen in the defaults section:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+># These sites require pop-ups too :(
+#
+{ -<A
+HREF="actions-file.html#KILL-POPUPS"
+>kill-popups</A
+> -<A
+HREF="actions-file.html#FILTER-POPUPS"
+>filter{popups}</A
+> }
+.dabs.com
+.overclockers.co.uk
+.deutsche-bank-24.de</PRE
+></TD
+></TR
+></TABLE
+></P
+><P
> The <TT
CLASS="LITERAL"
><A
><H3
CLASS="SECT3"
><A
-NAME="AEN3145"
-></A
->8.7.2. user.action</H3
+NAME="AEN2910">8.7.2. user.action</H3
><P
> So far we are painting with a broad brush by setting general policies,
which would be a reasonable starting point for many people. Now,
><TD
><PRE
CLASS="SCREEN"
-># Aliases are local to the file they are defined in.
-# (Re-)define aliases for this file:
+># (Re-)define aliases for this file:
#
{{alias}}
-#
-# These aliases just save typing later, and the alias names should
-# be self explanatory.
-#
-+crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
-crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- allow-all-cookies = -crunch-all-cookies -session-cookies-only
- allow-popups = -filter{all-popups} -kill-popups
-+block-as-image = +block +handle-as-image
--block-as-image = -block
-
-# These aliases define combinations of actions that are useful for
-# certain types of sites:
-#
+mercy-for-cookies = -crunch-all-cookies -session-cookies-only
fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
-shop = -crunch-all-cookies allow-popups
-
-# Allow ads for selected useful free sites:
-#
-allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}</PRE
+shop = mercy-for-cookies -filter{popups} -kill-popups
+allow-ads = -block -filter{banners-by-size} # (see below)</PRE
></TD
></TR
></TABLE
>
-
</P
><P
> Say you have accounts on some sites that you visit regularly, and
to allow persistent cookies for these sites. The
<TT
CLASS="LITERAL"
->allow-all-cookies</TT
+>mercy-for-cookies</TT
> alias defined above does exactly
- that, i.e. it disables crunching of cookies in any direction, and the
- processing of cookies to make them only temporary.</P
+ that, i.e. it disables crunching of cookies in any direction, and
+ processing of cookies to make them temporary.</P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
->{ allow-all-cookies }
+>{ mercy-for-cookies }
sunsolve.sun.com
slashdot.org
.yahoo.com
></TABLE
></P
><P
-> Your bank is allergic to some filter, but you don't know which, so you disable them all:</P
+> Your bank needs popups and is allergic to some filter, but you don't
+ know which, so you disable them all:</P
><P
> <TABLE
BORDER="0"
>{ -<A
HREF="actions-file.html#FILTER"
>filter</A
+> -<A
+HREF="actions-file.html#KILL-POPUPS"
+>kill-popups</A
> }
.your-home-banking-site.com</PRE
></TD
></TABLE
></P
><P
-> Some file types you may not want to filter.
- <SPAN
+> While browsing the web with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> makes no distinctions between regular web
- pages and downloads done via your web browser if it is an html or text type
- document.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-># A list of common file extensions that are likely to indicate raw text, and best
-# if unfiltered.
-/(.*/)?.*\.(pl|(s|p)?h|c(c|xx|pp)?|tcl|am|init?|cfg?|conf(ig)?|txt|rc|bat)$
-
-# Documentation should not need filtering (at least on some sites).
-.tldp.org</PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> Example of a simple <A
-HREF="actions-file.html#BLOCK"
->block</A
-> action. Say you've
- seen an ad on your favourite page on example.com that you want to get rid of.
- You have right-clicked the image, selected <SPAN
-CLASS="QUOTE"
->"copy image location"</SPAN
+> you
+ noticed some ads that sneaked through, but you were too lazy to
+ report them through our fine and easy <A
+HREF="contact.html"
+>feedback</A
>
- and pasted the URL below while removing the leading http://, into a
- <TT
-CLASS="LITERAL"
->{ +block }</TT
-> section. Note that <TT
-CLASS="LITERAL"
->{ +handle-as-image
- }</TT
-> need not be specified, since all URLs ending in
- <TT
-CLASS="LITERAL"
->.gif</TT
-> will be tagged as images by the general rules as set
- in default.action anyway:</P
+ system, so you have added them here:</P
><P
> <TABLE
BORDER="0"
HREF="actions-file.html#BLOCK"
>block</A
> }
-www.example.com/nasty-ads/sponsor.gif
-another.popular.site.net/more/junk/here/
-
-# Here we found one that is not in <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> default blocked list:
-.adfactory.net</PRE
+www.a-popular-site.com/some/unobvious/path
+another.popular.site.net/more/junk/here/</PRE
></TD
></TR
></TABLE
></P
><P
-> To force URLs that tend to have ad images, but it is difficult for
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> to know this since the ultimate returned
- object is obscured for one reason or another, we can try to force these to be
- treated as images (and thus avoid <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
+> Note that, assuming the banners in the above example have regular image
+ extensions (most do),
+ <TT
+CLASS="LITERAL"
+>+<A
+HREF="actions-file.html#HANDLE-AS-IMAGE"
+>handle-as-image</A
+></TT
>
- <SPAN
-CLASS="QUOTE"
->"BLOCKED"</SPAN
-> banner page). Note that if what is returned by the
- server turns out NOT to be an image, then your browser typically will display
- a broken icon image. Use cautiously.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->{ +block-as-image }
-# A shockwave ad, very annoying.
-.trip.com/.*\.swf
-.doubleclick.net
-/Realmedia/ads/
-adremote.</PRE
-></TD
-></TR
-></TABLE
-></P
+ need not be specified, since all URLs ending in these extensions will
+ already have been tagged as images in the relevant section of
+ <TT
+CLASS="FILENAME"
+>default.action</TT
+> by now.</P
><P
-> Now you noticed that the default configuration breaks Forbes Magazine,
+> Then you noticed that the default configuration breaks Forbes Magazine,
but you were too lazy to find out which action is the culprit, and you
were again too lazy to give <A
HREF="contact.html"
CLASS="LITERAL"
>fragile</TT
> alias on the site, and
- -- <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->whoa!</I
-></SPAN
-> -- it worked. The <TT
-CLASS="LITERAL"
->fragile</TT
->
- aliases disables those actions that are most likely to break a site. Also,
- good for testing purposes to see if it is <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- that is causing the problem or not.</P
+ -- whoa! -- it worked:</P
><P
><TABLE
BORDER="0"
>"fun"</SPAN
> filtering specified here.</P
><P
-> You might also worry about how your favourite free websites are
+> Finally, you might think about how your favourite free websites are
funded, and find that they rely on displaying banner advertisements
to survive. So you might want to specifically allow banners for those
sites that you feel provide value to you:</P
HREF="actions-file.html#BLOCK"
>block</A
></TT
->,
+>
<TT
CLASS="LITERAL"
>-<A
HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
>filter{banners-by-size}</A
></TT
->, and
- <TT
-CLASS="LITERAL"
->-<A
-HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
->filter{banners-by-link}</A
-></TT
-> above.</P
-><P
-> <TT
-CLASS="FILENAME"
->user.action</TT
-> is generally the best place to define
- exceptions and additions to the default policies of
- <TT
-CLASS="FILENAME"
->default.action</TT
->. Some actions are safe to have their
- default policies set here though. So let's set a default policy to have a
- <SPAN
-CLASS="QUOTE"
->"blank"</SPAN
-> image as opposed to the checkerboard pattern for
- <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->ALL</I
-></SPAN
-> sites. <SPAN
-CLASS="QUOTE"
->"/"</SPAN
-> of course matches all URL
- paths and patterns:</P
-><P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->{ +<A
-HREF="actions-file.html#SET-IMAGE-BLOCKER"
->set-image-blocker{blank}</A
-> }
-/ # ALL sites</PRE
-></TD
-></TR
-></TABLE
-></P
+>
+ above.</P
></DIV
></DIV
></DIV
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="See Also"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="APPENDIX"
-></A
->14. Appendix</H1
+NAME="APPENDIX">14. Appendix</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="REGEX"
-></A
->14.1. Regular Expressions</H2
+NAME="REGEX">14.1. Regular Expressions</H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN3727"
-></A
->14.2. <SPAN
+NAME="AEN3469">14.2. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>'s Internal Pages</H2
Privoxy main page:
</P
><A
-NAME="AEN3742"
-></A
-><BLOCKQUOTE
+NAME="AEN3484"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
editing of actions files:
</P
><A
-NAME="AEN3750"
-></A
-><BLOCKQUOTE
+NAME="AEN3492"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show the source code version numbers:
</P
><A
-NAME="AEN3755"
-></A
-><BLOCKQUOTE
+NAME="AEN3497"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show the browser's request headers:
</P
><A
-NAME="AEN3760"
-></A
-><BLOCKQUOTE
+NAME="AEN3502"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN3765"
-></A
-><BLOCKQUOTE
+NAME="AEN3507"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN3771"
-></A
-><BLOCKQUOTE
+NAME="AEN3513"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN3775"
-></A
-><BLOCKQUOTE
+NAME="AEN3517"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
</P
></BLOCKQUOTE
><A
-NAME="AEN3778"
-></A
-><BLOCKQUOTE
+NAME="AEN3520"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
><H3
CLASS="SECT3"
><A
-NAME="BOOKMARKLETS"
-></A
->14.2.1. Bookmarklets</H3
+NAME="BOOKMARKLETS">14.2.1. Bookmarklets</H3
><P
> Below are some <SPAN
CLASS="QUOTE"
><H2
CLASS="SECT2"
><A
-NAME="CHAIN"
-></A
->14.3. Chain of Events</H2
+NAME="CHAIN">14.3. Chain of Events</H2
><P
> Let's take a quick look at the basic sequence of events when a web page is
requested by your browser and <SPAN
><H2
CLASS="SECT2"
><A
-NAME="ACTIONSANAT"
-></A
->14.4. Anatomy of an Action</H2
+NAME="ACTIONSANAT">14.4. Anatomy of an Action</H2
><P
> The way <SPAN
CLASS="APPLICATION"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="CONFIG"
-></A
->7. The Main Configuration File</H1
+NAME="CONFIG">7. The Main Configuration File</H1
><P
> Again, the main configuration file is named <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="CONF-LOG-LOC"
-></A
->7.1. Configuration and Log File Locations</H2
+NAME="CONF-LOG-LOC">7.1. Configuration and Log File Locations</H2
><P
> <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="CONFDIR"
-></A
->7.1.1. confdir</H4
+NAME="CONFDIR">7.1.1. confdir</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="LOGDIR"
-></A
->7.1.2. logdir</H4
+NAME="LOGDIR">7.1.2. logdir</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ACTIONSFILE"
-></A
->7.1.3. actionsfile</H4
+NAME="ACTIONSFILE">7.1.3. actionsfile</H4
><A
NAME="DEFAULT.ACTION"
></A
><H4
CLASS="SECT3"
><A
-NAME="FILTERFILE"
-></A
->7.1.4. filterfile</H4
+NAME="FILTERFILE">7.1.4. filterfile</H4
><A
NAME="DEFAULT.FILTER"
></A
><H4
CLASS="SECT3"
><A
-NAME="LOGFILE"
-></A
->7.1.5. logfile</H4
+NAME="LOGFILE">7.1.5. logfile</H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
+> The windows version will additionally log to the console.
+ </P
+><P
> The logfile is where all logging and error messages are written. The level
of detail and number of messages are set with the <TT
CLASS="LITERAL"
><H4
CLASS="SECT3"
><A
-NAME="JARFILE"
-></A
->7.1.6. jarfile</H4
+NAME="JARFILE">7.1.6. jarfile</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="TRUSTFILE"
-></A
->7.1.7. trustfile</H4
+NAME="TRUSTFILE">7.1.7. trustfile</H4
><P
></P
><DIV
>Effect if unset:</DT
><DD
><P
-> The entire trust mechanism is turned off.
+> The whole trust mechanism is turned off.
</P
></DD
><DT
CLASS="APPLICATION"
>Privoxy</SPAN
> will only allow
- access to sites that are specified in the trustfile. Sites can be listed
- in one of two ways:
- </P
-><P
-> Prepending a <TT
-CLASS="LITERAL"
->~</TT
-> character limits access to this site
- only (and any sub-paths within this site), e.g.
- <TT
-CLASS="LITERAL"
->~www.example.com</TT
->.
- </P
-><P
-> Or, you can designate sites as <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->trusted referrers</I
-></SPAN
->, by
- prepending the name with a <TT
+ access to sites that are named in the trustfile.
+ You can also mark sites as trusted referrers (with <TT
CLASS="LITERAL"
>+</TT
-> character. The effect is that
- access to untrusted sites will be granted -- but only if a link from this
- trusted referrer was used. The link target will then be added to the
- <SPAN
+>), with
+ the effect that access to untrusted sites will be granted, if a link from a
+ trusted referrer was used.
+ The link target will then be added to the <SPAN
CLASS="QUOTE"
>"trustfile"</SPAN
-> so that future, direct accesses will be granted.
- Sites added via this mechanism do not become trusted referrers themselves
- (i.e. they are added with a <TT
-CLASS="LITERAL"
->~</TT
-> designation).
+>.
+ Possible applications include limiting Internet access for children.
</P
><P
-> If you use the <TT
+> If you use <TT
CLASS="LITERAL"
>+</TT
-> operator in the trust file, it may grow
- considerably over time.
- </P
-><P
-> It is recommended that <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> be compiled with
- the <TT
-CLASS="LITERAL"
->--disable-force</TT
->, <TT
-CLASS="LITERAL"
->--disable-toggle</TT
-> and
- <TT
-CLASS="LITERAL"
-> --disable-editor</TT
-> options, if this feature is to be
- used.
- </P
-><P
-> Possible applications include limiting Internet access for children.
+> operator in the trust file, it may grow considerably over time.
</P
></DD
></DL
><H2
CLASS="SECT2"
><A
-NAME="LOCAL-SET-UP"
-></A
->7.2. Local Set-up Documentation</H2
+NAME="LOCAL-SET-UP">7.2. Local Set-up Documentation</H2
><P
> If you intend to operate <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="USER-MANUAL"
-></A
->7.2.1. user-manual</H4
+NAME="USER-MANUAL">7.2.1. user-manual</H4
><P
></P
><DIV
><TD
><PRE
CLASS="SCREEN"
-> user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> Windows, in local filesystem, <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->must</I
-></SPAN
-> use forward slash notation:
- </P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> user-manual file:/c:/some-dir/privoxy-3.0.1/user-manual/</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> Windows, UNC notation (with forward slashes):
- </P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> user-manual file://///some-server/some-path/privoxy-3.0.1/user-manual/</PRE
+>user-manual file:///usr/share/doc/privoxy-3.0.0/user-manual/</PRE
></TD
></TR
></TABLE
><TD
><PRE
CLASS="SCREEN"
-> user-manual http://local-webserver/privoxy-user-manual/</PRE
+>user-manual http://local-webserver/privoxy-user-manual/</PRE
></TD
></TR
></TABLE
><H4
CLASS="SECT3"
><A
-NAME="TRUST-INFO-URL"
-></A
->7.2.2. trust-info-url</H4
+NAME="TRUST-INFO-URL">7.2.2. trust-info-url</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ADMIN-ADDRESS"
-></A
->7.2.3. admin-address</H4
+NAME="ADMIN-ADDRESS">7.2.3. admin-address</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="PROXY-INFO-URL"
-></A
->7.2.4. proxy-info-url</H4
+NAME="PROXY-INFO-URL">7.2.4. proxy-info-url</H4
><P
></P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="DEBUGGING"
-></A
->7.3. Debugging</H2
+NAME="DEBUGGING">7.3. Debugging</H2
><P
> These options are mainly useful when tracing a problem.
Note that you might also want to invoke
><H4
CLASS="SECT3"
><A
-NAME="DEBUG"
-></A
->7.3.1. debug</H4
+NAME="DEBUG">7.3.1. debug</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SINGLE-THREADED"
-></A
->7.3.2. single-threaded</H4
+NAME="SINGLE-THREADED">7.3.2. single-threaded</H4
><P
></P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="ACCESS-CONTROL"
-></A
->7.4. Access Control and Security</H2
+NAME="ACCESS-CONTROL">7.4. Access Control and Security</H2
><P
> This section of the config file controls the security-relevant aspects
of <SPAN
><H4
CLASS="SECT3"
><A
-NAME="LISTEN-ADDRESS"
-></A
->7.4.1. listen-address</H4
+NAME="LISTEN-ADDRESS">7.4.1. listen-address</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="TOGGLE"
-></A
->7.4.2. toggle</H4
+NAME="TOGGLE">7.4.2. toggle</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-REMOTE-TOGGLE"
-></A
->7.4.3. enable-remote-toggle</H4
+NAME="ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-EDIT-ACTIONS"
-></A
->7.4.4. enable-edit-actions</H4
+NAME="ENABLE-EDIT-ACTIONS">7.4.4. enable-edit-actions</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ACLS"
-></A
->7.4.5. ACLs: permit-access and deny-access</H4
+NAME="ACLS">7.4.5. ACLs: permit-access and deny-access</H4
><A
NAME="PERMIT-ACCESS"
></A
><H4
CLASS="SECT3"
><A
-NAME="BUFFER-LIMIT"
-></A
->7.4.6. buffer-limit</H4
+NAME="BUFFER-LIMIT">7.4.6. buffer-limit</H4
><P
></P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="FORWARDING"
-></A
->7.5. Forwarding</H2
+NAME="FORWARDING">7.5. Forwarding</H2
><P
> This feature allows routing of HTTP requests through a chain of
multiple proxies.
><H4
CLASS="SECT3"
><A
-NAME="FORWARD"
-></A
->7.5.1. forward</H4
+NAME="FORWARD">7.5.1. forward</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SOCKS"
-></A
->7.5.2. forward-socks4 and forward-socks4a</H4
+NAME="SOCKS">7.5.2. forward-socks4 and forward-socks4a</H4
><A
NAME="FORWARD-SOCKS4"
></A
><H4
CLASS="SECT3"
><A
-NAME="ADVANCED-FORWARDING-EXAMPLES"
-></A
->7.5.3. Advanced Forwarding Examples</H4
+NAME="ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding Examples</H4
><P
> If you have links to multiple ISPs that provide various special content
only to their subscribers, you can configure multiple <SPAN
><H2
CLASS="SECT2"
><A
-NAME="WINDOWS-GUI"
-></A
->7.6. Windows GUI Options</H2
+NAME="WINDOWS-GUI">7.6. Windows GUI Options</H2
><P
> <SPAN
CLASS="APPLICATION"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="CONFIGURATION"
-></A
->6. <SPAN
+NAME="CONFIGURATION">6. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> Configuration</H1
><H2
CLASS="SECT2"
><A
-NAME="AEN650"
-></A
->6.1. Controlling <SPAN
+NAME="AEN579">6.1. Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> with Your Web Browser</H2
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN659"
-></A
-> Privoxy Menu</H2
+NAME="AEN588"> Privoxy Menu</H2
><P
></P
><TABLE
><TR
><TD
> ▪ <A
-HREF="http://www.privoxy.org/3.0.1/user-manual/"
+HREF="http://www.privoxy.org/3.0.0/user-manual/"
TARGET="_top"
>Documentation</A
>
><H2
CLASS="SECT2"
><A
-NAME="CONFOVERVIEW"
-></A
->6.2. Configuration Files Overview</H2
+NAME="CONFOVERVIEW">6.2. Configuration Files Overview</H2
><P
> For Unix, *BSD and Linux, all configuration files are located in
<TT
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Templates"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="CONTACT"
-></A
->11. Contacting the Developers, Bug Reporting and Feature
+NAME="CONTACT">11. Contacting the Developers, Bug Reporting and Feature
Requests</H1
><P
> We value your feedback. In fact, we rely on it to improve
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT"
-></A
->11.1. Get Support</H2
+NAME="CONTACT-SUPPORT">11.1. Get Support</H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS"
-></A
->11.2. Report Bugs</H2
+NAME="CONTACT-BUGS">11.2. Report Bugs</H2
><P
> Please report all bugs <SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE"
-></A
->11.3. Request New Features</H2
+NAME="CONTACT-FEATURE">11.3. Request New Features</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"
-></A
->11.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS">11.4. Report Ads or Other Actions-Related Problems</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"
-></A
->11.5. Other</H2
+NAME="CONTACT-OTHER">11.5. Other</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!
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Contacting the Developers, Bug Reporting and Feature
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT"
-></A
->12. <SPAN
+NAME="COPYRIGHT">12. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> Copyright, License and History</H1
><H2
CLASS="SECT2"
><A
-NAME="AEN3473"
-></A
->12.1. License</H2
+NAME="AEN3215">12.1. License</H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="HISTORY"
-></A
->12.2. History</H2
+NAME="HISTORY">12.2. History</H2
><P
> In the beginning, there was the
<A
><H2
CLASS="SECT2"
><A
-NAME="AUTHORS"
-></A
->12.3. Authors</H2
+NAME="AUTHORS">12.3. Authors</H2
><P
> Current Project Developers:</P
><P
> Current Project Contributors:</P
><P
CLASS="LITERALLAYOUT"
-> Johny Agotnes <br>
- Rodrigo Barbosa (RPM specfiles)<br>
+> Rodrigo Barbosa (RPM specfiles)<br>
Moritz Barsnick<br>
Hal Burgiss (docs)<br>
- Mattes Dolak <br>
Karsten Hopp (Red Hat)<br>
Alexander Lazic<br>
- Daniel Leite<br>
Gábor Lipták<br>
- Andrew Lock (Win32)<br>
- Guy Laroche<br>
+ Guy<br>
Haroon Rafique<br>
Roland Rosenfeld (Debian)<br>
Georg Sauthoff (Gentoo)<br>
David Schmidt (OS/2, Mac OSX ports)<br>
Joerg Strohmayer (Amiga)<br>
- Sviatoslav Sviridov<br>
Sarantis Paskalis</P
><P
> Based in part on code originally developed by:</P
Andrew J. Caines<br>
Clifford Caoile<br>
Michael T. Davis<br>
- Brian Dessent<br>
Peter E<br>
Aaron Hamid<br>
Magnus Holmgren<br>
- Don Libes <br>
+ Daniel Leite<br>
Paul Lieverse<br>
- David Mediavilla <br>
- Oliver Stoeneberg<br>
Roberto Ragusa<br>
Maynard Riley<br>
Bart Schelstraete<br>
Darren Wiebe<br>
- Jamie Zawinski</P
+ jwz</P
></DIV
></DIV
><DIV
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="FILTER-FILE"
-></A
->9. The Filter File</H1
+NAME="FILTER-FILE">9. The Filter File</H1
><P
> All text substitutions that can be invoked through the
<TT
><H2
CLASS="SECT2"
><A
-NAME="AEN3271"
-></A
->9.1. Filter File Tutorial</H2
+NAME="AEN3013">9.1. Filter File Tutorial</H2
><P
> Now, let's complete our <SPAN
CLASS="QUOTE"
<HTML
><HEAD
><TITLE
->Privoxy 3.0.1 User Manual</TITLE
+>Privoxy 3.0.0 User Manual</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
><H1
CLASS="TITLE"
><A
-NAME="AEN2"
-></A
->Privoxy 3.0.1 User Manual</H1
+NAME="AEN2">Privoxy 3.0.0 User Manual</H1
><P
CLASS="PUBDATE"
> <SUB
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 1.123.2.27 2003/03/18 19:37:14 oes Exp $<BR></P
+>$Id: user-manual.sgml,v 1.123.2.18 2002/08/22 23:47:58 hal9 Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"
-></A
-><P
+NAME="AEN9"><P
></P
><P
> The <I
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN650"
+HREF="configuration.html#AEN579"
>Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN1818"
+HREF="actions-file.html#AEN1640"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN1825"
+HREF="actions-file.html#AEN1647"
>How to Edit</A
></DT
><DT
><DL
><DT
>8.4.1. <A
-HREF="actions-file.html#AEN1898"
+HREF="actions-file.html#AEN1711"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN1960"
+HREF="actions-file.html#AEN1773"
>The Path Pattern</A
></DT
></DL
></DT
><DT
>8.5.21. <A
-HREF="actions-file.html#AEN2914"
+HREF="actions-file.html#AEN2701"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN2979"
+HREF="actions-file.html#AEN2753"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN3145"
+HREF="actions-file.html#AEN2910"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN3271"
+HREF="filter-file.html#AEN3013"
>Filter File Tutorial</A
></DT
></DL
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN3473"
+HREF="copyright.html#AEN3215"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN3727"
+HREF="appendix.html#AEN3469"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION"
-></A
->2. Installation</H1
+NAME="INSTALLATION">2. Installation</H1
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-PACKAGES"
-></A
->2.1. Binary Packages</H2
+NAME="INSTALLATION-PACKAGES">2.1. Binary Packages</H2
><P
>How to install the binary packages depends on your operating system:</P
><DIV
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-RPM"
-></A
->2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
+NAME="INSTALLATION-PACK-RPM">2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-3.0.1-1.rpm</TT
+>rpm -Uvh privoxy-3.0.0-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-3.0.1-1.src.rpm</TT
+>rpm --rebuild privoxy-3.0.0-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-DEB"
-></A
->2.1.2. Debian</H3
+NAME="INSTALLATION-DEB">2.1.2. Debian</H3
><P
> DEBs can be installed with <TT
CLASS="LITERAL"
>dpkg -i
- privoxy_3.0.1-1.deb</TT
+ privoxy_3.0.0-1.deb</TT
>, and will use
<TT
CLASS="FILENAME"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-WIN"
-></A
->2.1.3. Windows</H3
+NAME="INSTALLATION-PACK-WIN">2.1.3. Windows</H3
><P
> Just double-click the installer, which will guide you through
the installation process. You will find the configuration files
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-BINTGZ"
-></A
->2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
+NAME="INSTALLATION-PACK-BINTGZ">2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
><P
> Create a new directory, <TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-OS2"
-></A
->2.1.5. OS/2</H3
+NAME="INSTALLATION-OS2">2.1.5. OS/2</H3
><P
> First, make sure that no previous installations of
<SPAN
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-MAC"
-></A
->2.1.6. Mac OSX</H3
+NAME="INSTALLATION-MAC">2.1.6. Mac OSX</H3
><P
> Unzip the downloaded file (you can either double-click on the file
from the finder, or from the desktop if you downloaded it there).
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-AMIGA"
-></A
->2.1.7. AmigaOS</H3
+NAME="INSTALLATION-AMIGA">2.1.7. AmigaOS</H3
><P
> Copy and then unpack the <TT
CLASS="FILENAME"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATTION-GENTOO"
-></A
->2.1.8. Gentoo</H3
+NAME="INSTALLATTION-GENTOO">2.1.8. Gentoo</H3
><P
> Gentoo source packages (Ebuilds) for <SPAN
CLASS="APPLICATION"
>, the
documentation is in <TT
CLASS="FILENAME"
->/usr/share/doc/privoxy-3.0.1</TT
+>/usr/share/doc/privoxy-3.0.0</TT
>
and the Log directory is in <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-SOURCE"
-></A
->2.2. Building from Source</H2
+NAME="INSTALLATION-SOURCE">2.2. Building from Source</H2
><P
> The most convenient way to obtain the <SPAN
CLASS="APPLICATION"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz]
- cd privoxy-3.0.1</PRE
+> tar xzvf privoxy-3.0.0-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.0</PRE
></TD
></TR
></TABLE
>, which will
contain the source tree.</P
><P
-> You can also check out any <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- <SPAN
-CLASS="QUOTE"
->"branch"</SPAN
->, just exchange the <SPAN
-CLASS="APPLICATION"
->current</SPAN
->
- name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs
- tree).</P
-><P
-> It is also strongly recommended to not run <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- as root, and instead it is suggested to create a <SPAN
-CLASS="QUOTE"
->"privoxy"</SPAN
-> user
- and group for this purpose. See your local documentation for the correct
- command line to do this.</P
-><P
-> <TT
-CLASS="FILENAME"
->/etc/passwd</TT
-> might then look like:</P
+> Then, in either case, to build from unpacked tarball or CVS source:</P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
+> autoheader
+ autoconf
+ ./configure # (--help to see options)
+ make # (the make from gnu, gmake for *BSD)
+ su
+ make -n install # (to see where all the files will go)
+ make install # (to really install)</PRE
></TD
></TR
></TABLE
></P
+><DIV
+CLASS="WARNING"
><P
-> And then <TT
-CLASS="FILENAME"
->/etc/group</TT
->, like:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+></P
+><TABLE
+CLASS="WARNING"
+BORDER="1"
WIDTH="100%"
><TR
><TD
-><PRE
-CLASS="SCREEN"
-> privoxy:*:7777:</PRE
+ALIGN="CENTER"
+><B
+>Warning</B
></TD
></TR
-></TABLE
-></P
-><P
-> Some binary packages may do this for you.</P
-><P
-> Then, to build from either unpacked tarball or CVS source:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
><TR
><TD
-><PRE
-CLASS="SCREEN"
-> autoheader
- autoconf
- ./configure # (--help to see options)
- make # (the make from gnu, gmake for *BSD)
- su
- make -n install # (to see where all the files will go)
- make -s install # (to really install, -s to silence output)</PRE
+ALIGN="LEFT"
+><P
+>
+ The <SPAN
+CLASS="QUOTE"
+>"make install"</SPAN
+> target is temporary quite broken! It is
+ recommended to use a binary package, or do a source build, and manually
+ install the components. Sorry.
+ </P
></TD
></TR
></TABLE
-></P
+></DIV
><P
-> If you have GNU <B
-CLASS="COMMAND"
->make</B
->, you can have the first four steps
+> If you have gnu make, you can have the first four steps
automatically done for you by just typing:</P
><P
> <TABLE
><P
> in the freshly downloaded or unpacked source directory.</P
><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->WARNING:</I
-></SPAN
-> If installing as root, the install will fail
- unless another user is specified. <B
-CLASS="COMMAND"
->configure</B
-> accepts
- <TT
-CLASS="LITERAL"
->--with-user</TT
-> and <TT
-CLASS="LITERAL"
->--with-group</TT
-> options
- for setting user and group ownership of the configuration files (which need
- to be writable by the daemon). The specified <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->user must already
- exist</I
-></SPAN
->. Or if there is already a privoxy user on the system, and no
- user was specified during configure, <B
-CLASS="COMMAND"
->make install</B
-> then
- will use the privoxy user. When starting <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->,
- it should be run as this same user that owns the configuration and log
- files.</P
-><P
-> Alternately, you can specify <TT
-CLASS="LITERAL"
->user</TT
-> and <TT
-CLASS="LITERAL"
->group</TT
->
- on the <B
-CLASS="COMMAND"
->make</B
-> command line, but be sure both already exist:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> make -s install USER=privoxy GROUP=privoxy</PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> If no <TT
-CLASS="LITERAL"
->group</TT
-> is specified, the install will assume a group
- exists with the same name as the specified <TT
-CLASS="LITERAL"
->user</TT
->.</P
-><P
-> The default installation path for <B
-CLASS="COMMAND"
->make install</B
-> is
- <TT
-CLASS="FILENAME"
->/usr/local</TT
->. This may of course be customized with
- the various <B
-CLASS="COMMAND"
->./configure</B
-> path options. If you are doing
- a root install to anywhere else besides <TT
-CLASS="FILENAME"
->/usr/local</TT
->, be
- sure to set the appropriate paths with the correct configure options
- (<B
-CLASS="COMMAND"
->./configure --help</B
->).</P
-><P
-> If you do install to <TT
-CLASS="FILENAME"
->/usr/local</TT
->, the install will use
- <TT
-CLASS="LITERAL"
->sysconfdir=$prefix/etc/privoxy</TT
-> by default. All other
- destinations, and the direct usage of <TT
-CLASS="LITERAL"
->--sysconfdir</TT
-> flag
- behave like normal, i.e. will not add the extra <TT
-CLASS="FILENAME"
->privoxy</TT
->
- directory. This is for a safer install, as there may already exist another
- program that uses a file with the <SPAN
-CLASS="QUOTE"
->"config"</SPAN
-> name, and thus makes
- <TT
-CLASS="FILENAME"
->/usr/local/etc</TT
-> cleaner.</P
-><P
-> If installing to <TT
-CLASS="FILENAME"
->/usr/local</TT
->, the docs will go by default
- to <TT
-CLASS="FILENAME"
->$prefix/share/doc</TT
->. But if this directory doesn't
- exist, it will then try <TT
-CLASS="FILENAME"
->$prefix/doc</TT
-> and install there before
- creating a new <TT
-CLASS="FILENAME"
->$prefix/share/doc</TT
-> just for
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->.</P
-><P
-> Again, if the installs goes to <TT
-CLASS="FILENAME"
->/usr/local</TT
->, the
- <TT
-CLASS="LITERAL"
->localstatedir</TT
-> (ie: <TT
-CLASS="FILENAME"
->var/</TT
->) will default
- to <TT
-CLASS="FILENAME"
->/var</TT
-> instead of <TT
-CLASS="LITERAL"
->$prefix/var</TT
-> so
- the logs will go to <TT
-CLASS="FILENAME"
->/var/log/privoxy/</TT
->, and the pid file
- will be created in <TT
-CLASS="FILENAME"
->/var/run/privoxy.pid</TT
->. </P
-><P
-> <B
-CLASS="COMMAND"
->make install</B
-> will attempt to set the correct values
- in <TT
-CLASS="FILENAME"
->config</TT
-> (main configuration file). You may want
- to check this to make sure all values are correct. If appropriate,
- an init script will be installed, but it is up to the user to determine
- how and where to start <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->. The init
- script should be checked for correct paths and values, if anything other than
- a default install is done.</P
-><P
-> If install finds previous versions of any configuration files, these will not
- be overwritten, and the new ones will be installed with a <SPAN
-CLASS="QUOTE"
->"new"</SPAN
->
- extension. You will then need to manually update the installed configuration
- files as needed. All template files will be overwritten. If you have
- customized, local templates, you should save these first. If a previous
- version of <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is already running, you will
- have to restart it manually.</P
-><P
> For more detailed instructions on how to build Redhat and SuSE RPMs,
Windows self-extracting installers, building on platforms with
special requirements etc, please consult the <A
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-KEEPUPDATED"
-></A
->2.3. Keeping your Installation Up-to-Date</H2
+NAME="INSTALLATION-KEEPUPDATED">2.3. Keeping your Installation Up-to-Date</H2
><P
> As user feedback comes in and development continues, we will make updated versions
of both the main <A
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="INTRODUCTION"
-></A
->1. Introduction</H1
+NAME="INTRODUCTION">1. Introduction</H1
><P
> This documentation is included with the current stable version of
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.3.0.1.</P
+>, v.3.0.0.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="FEATURES"
-></A
->1.1. Features</H2
+NAME="FEATURES">1.1. Features</H2
><P
> In addition to <SPAN
CLASS="APPLICATION"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Privoxy 3.0.1 User Manual</TD
+>Privoxy 3.0.0 User Manual</TD
><TD
WIDTH="34%"
ALIGN="center"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Note to Upgraders"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="QUICKSTART"
-></A
->4. Quickstart to Using <SPAN
+NAME="QUICKSTART">4. Quickstart to Using <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></H1
CLASS="APPLICATION"
>Privoxy</SPAN
> as HTTP and
- HTTPS (SSL) proxy by setting the proxy configuration for address of
+ HTTPS proxy by setting the proxy configuration for address of
<TT
CLASS="LITERAL"
>127.0.0.1</TT
><LI
><P
> Flush your browser's disk and memory caches, to remove any cached ad images.
- If using <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> to manage cookies, you should
- remove any currently stored cookies too.
</P
></LI
><LI
><H2
CLASS="SECT2"
><A
-NAME="QUICKSTART-AD-BLOCKING"
-></A
->4.1. Quickstart to Ad Blocking</H2
+NAME="QUICKSTART-AD-BLOCKING">4.1. Quickstart to Ad Blocking</H2
><P
> Ad blocking is but one of <SPAN
CLASS="APPLICATION"
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN454"
-></A
-><P
+NAME="AEN388"><P
><B
>Figure 1. Actions Files in Use</B
></P
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Copyright, License and History"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="SEEALSO"
-></A
->13. See Also</H1
+NAME="SEEALSO">13. See Also</H1
><P
> Other references and sites of interest to <SPAN
CLASS="APPLICATION"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="STARTUP"
-></A
->5. Starting <SPAN
+NAME="STARTUP">5. Starting <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></H1
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN505"
-></A
-><P
+NAME="AEN439"><P
><B
>Figure 2. Proxy Configuration (Mozilla)</B
></P
><H2
CLASS="SECT2"
><A
-NAME="START-REDHAT"
-></A
->5.1. Red Hat and Conectiva</H2
+NAME="START-REDHAT">5.1. Red Hat and Conectiva</H2
><P
> We use a script. Note that Red Hat does not start Privoxy upon booting per
default. It will use the file <TT
><H2
CLASS="SECT2"
><A
-NAME="START-DEBIAN"
-></A
->5.2. Debian</H2
+NAME="START-DEBIAN">5.2. Debian</H2
><P
> We use a script. Note that Debian starts Privoxy upon booting per
default. It will use the file
><H2
CLASS="SECT2"
><A
-NAME="START-SUSE"
-></A
->5.3. SuSE</H2
+NAME="START-SUSE">5.3. SuSE</H2
><P
>We use a script. It will use the file <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="START-WINDOWS"
-></A
->5.4. Windows</H2
+NAME="START-WINDOWS">5.4. Windows</H2
><P
>Click on the Privoxy Icon to start Privoxy. If no configuration file is
specified on the command line, <SPAN
><H2
CLASS="SECT2"
><A
-NAME="START-UNICES"
-></A
->5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</H2
+NAME="START-UNICES">5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</H2
><P
>Example Unix startup command:</P
><P
><H2
CLASS="SECT2"
><A
-NAME="START-OS2"
-></A
->5.6. OS/2</H2
+NAME="START-OS2">5.6. OS/2</H2
><P
> During installation, <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="START-MACOSX"
-></A
->5.7. Mac OSX</H2
+NAME="START-MACOSX">5.7. Mac OSX</H2
><P
> During installation, <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="START-AMIGAOS"
-></A
->5.8. AmigaOS</H2
+NAME="START-AMIGAOS">5.8. AmigaOS</H2
><P
> Start <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="START-GENTOO"
-></A
->5.9. Gentoo</H2
+NAME="START-GENTOO">5.9. Gentoo</H2
><P
> A script is again used. It will use the file <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="CMDOPTIONS"
-></A
->5.10. Command Line Options</H2
+NAME="CMDOPTIONS">5.10. Command Line Options</H2
><P
> <SPAN
CLASS="APPLICATION"
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->--chroot</I
-></SPAN
->
-
- </P
-><P
-> Before changing to the user ID given in the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->--user</I
-></SPAN
-> option,
- chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy
- process that the directory tree starts there. If set up carefully, this can limit
- the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy.
- Unix only.
- </P
-></LI
-><LI
-><P
> <SPAN
CLASS="emphasis"
><I
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Filter File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="TEMPLATES"
-></A
->10. Templates</H1
+NAME="TEMPLATES">10. Templates</H1
><P
> All <SPAN
CLASS="APPLICATION"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.0 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.0 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="UPGRADERSNOTE"
-></A
->3. Note to Upgraders</H1
+NAME="UPGRADERSNOTE">3. Note to Upgraders</H1
><P
> There are very significant changes from earlier
<SPAN
-# $Id: privoxy-rh.spec,v 1.33.2.19 2002/08/25 23:36:03 hal9 Exp $
+# $Id: privoxy-rh.spec,v 1.33.2.18 2002/08/10 11:28:50 oes Exp $
#
# Written by and Copyright (C) 2001 the SourceForge
# Privoxy team. http://www.privoxy.org/
# ATTENTION
# Version and release should be updated acordingly on configure.in and
# configure. Otherwise, the package can be build with the wrong value
-Version: 3.0.1
+Version: 3.0.0
Release: 1
Summary: Privoxy - privacy enhancing proxy
License: GPL
%{_mandir}/man1/%{name}.*
%changelog
-* Wed Mar 19 2003 Hal Burgiss <hal@foobox.net>
-- Bump version for 3.0.1.
-
* Tue Aug 25 2002 Hal Burgiss <hal@foobox.net>
- Bump version for 3.0.0 :)
additional "-r @" flag.
# $Log: privoxy-rh.spec,v $
-# Revision 1.33.2.19 2002/08/25 23:36:03 hal9
-# Bump version for 3.0.0.
-#
# Revision 1.33.2.18 2002/08/10 11:28:50 oes
# Bumped version
#
-# $Id: privoxy-suse.spec,v 1.20.2.7 2002/08/25 23:36:03 hal9 Exp $
+# $Id: privoxy-suse.spec,v 1.20.2.6 2002/08/10 11:28:50 oes Exp $
#
# Written by and Copyright (C) 2001 the SourceForge
# Privoxy team. http://www.privoxy.org/
Vendor: Privoxy.Org
Name: privoxy-suse
Distribution: defineme
-Version: 3.0.1
+Version: 3.0.0
Release: 1
# Needs makefile change: Source: http://prdownloads.sourceforge.net/ijbswa/privoxy-%{version}-%{status}-src.tar.gz
Source: http://prdownloads.sourceforge.net/ijbswa/privoxy-%{version}.tar.gz
# -----------------------------------------------------------------------------
#
%changelog
-* Wed Mar 19 2003 Hal Burgiss <hal@foobox.net>
-- Bump version for 3.0.1.
-
* Tue Aug 25 2002 Hal Burgiss <hal@foobox.net>
- Bump version for 3.0.0 :)
- new package: version 2.0
# $Log: privoxy-suse.spec,v $
-# Revision 1.20.2.7 2002/08/25 23:36:03 hal9
-# Bump version for 3.0.0.
-#
# Revision 1.20.2.6 2002/08/10 11:28:50 oes
# Bumped version
#
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "PRIVOXY" "1" "19 March 2003" "Privoxy 3.0.1" ""
+.TH "PRIVOXY" "1" "26 August 2002" "Privoxy 3.0.0" ""
.SH NAME
privoxy \- Privacy Enhancing Proxy
.SH SYNOPSIS
\fIgroup\fR was not given, the default group of
\fIuser\fR. Exit if the privileges are not
sufficient to do so.
-.TP
-\fB--chroot\fR
-Before changing to the user ID given in the --user option, chroot to
-that user's home directory, i.e. make the kernel pretend to the
-\fBPrivoxy\fR process that the directory tree starts
-there. If set up carefully, this can limit the impact of possible
-vulnerabilities in \fBPrivoxy\fR to the files contained in
-that hierarchy.
.PP
If the \fIconfigfile\fR is not specified on the command line,
\fBPrivoxy\fR will look for a file named
.SH "DEVELOPMENT TEAM"
.nf
- Andreas Oesterhelt (lead developer)
- Hal Burgiss (docs)
- David Schmidt (OS/2, Mac OSX ports)
-
- Johny Agotnes
+ Jon Foster
+ Andreas Oesterhelt
+ Stefan Waldherr
+ Thomas Steudten
+ Rodney Stromlund
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
- Mattes Dolak
- Jon Foster
+ Hal Burgiss (docs)
Karsten Hopp (Red Hat)
Alexander Lazic
- Daniel Leite
Gábor Lipták
- Andrew Lock (Win32)
- Guy Laroche
+ Guy
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
- Thomas Steudten
+ David Schmidt (OS/2, Mac OSX ports)
Joerg Strohmayer (Amiga)
- Rodney Stromlund
- Sviatoslav Sviridov
Sarantis Paskalis
- Stefan Waldherr
.fi
.SH "COPYRIGHT AND LICENSE"
.SS "COPYRIGHT"
-const char w32taskbar_rcs[] = "$Id: w32taskbar.c,v 1.7.2.1 2002/11/20 14:39:32 oes Exp $";
+const char w32taskbar_rcs[] = "$Id: w32taskbar.c,v 1.7 2002/03/31 17:19:00 jongfoster Exp $";
/*********************************************************************
*
* File : $Source: /cvsroot/ijbswa/current/Attic/w32taskbar.c,v $
*
* Revisions :
* $Log: w32taskbar.c,v $
- * Revision 1.7.2.1 2002/11/20 14:39:32 oes
- * Applied patch by Mattes Dolak which adds re-creation of the win32 taskbar
- * icon on reception of the "TaskbarCreated" window message.
- *
* Revision 1.7 2002/03/31 17:19:00 jongfoster
* Win32 only: Enabling STRICT to fix a VC++ compile warning.
*
if (msg == g_traycreatedmsg)
{
- TrayAddIcon(g_hwndTrayX, 1, g_hiconApp, "Privoxy");
+ TrayAddIcon(g_hwndTray, 1, g_hiconApp, "Privoxy");
}
break;
}
projects / privoxy.git / commitdiff