>Configuration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="misc.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONFIGURATION">3. Configuration</H1
+NAME="CONFIGURATION"
+>3. Configuration</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="NEWCONFIG">3.1. Can I use my old config files?</H3
+NAME="GETUPDATES"
+>3.1. Where can I get updated Actions Files?</A
+></H3
+><P
+> Based on your feedback and the continuing development, updated actions files will be
+ made available on the <A
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>files section</A
+> of
+ our <A
+HREF="http://sf.net/projects/ijbswa/"
+TARGET="_top"
+>project page</A
+>.
+ </P
+><P
+> If you wish to receive an email notification whenever we release updates of
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> or the actions file, <A
+HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
+TARGET="_top"
+>subscribe
+ to our announce mailing list</A
+>, ijbswa-announce@lists.sourceforge.net.
+ </P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="NEWCONFIG"
+>3.2. Can I use my old config files?</A
+></H3
><P
> The syntax, number, and purpose of configuration files has substantially
changed from <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN258">3.2. What is an <SPAN
+NAME="AEN266"
+>3.3. What is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
-> file?</H3
+> file?</A
+></H3
><P
> <A
HREF="../user-manual/actions-file.html"
><H3
CLASS="SECT2"
><A
-NAME="ACTIONSS">3.3. The <SPAN
+NAME="ACTIONSS"
+>3.4. The <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> concept confuses me. Please list
some of these <SPAN
CLASS="QUOTE"
>"actions"</SPAN
->.</H3
+>.</A
+></H3
><P
> For a comprehensive discussion of the actions concept, please refer
to the <A
><H3
CLASS="SECT2"
><A
-NAME="AEN277">3.4. How are actions files configured? What is the easiest
-way to do this?</H3
+NAME="AEN285"
+>3.5. How are actions files configured? What is the easiest
+way to do this?</A
+></H3
><P
> Actions files are just text files in a special syntax and can be edited
with a text editor. The probably easiest way is to access
><H3
CLASS="SECT2"
><A
-NAME="AEN285">3.5. There are several different <SPAN
+NAME="AEN293"
+>3.6. There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> files. What are
-the differences?</H3
+the differences?</A
+></H3
><P
> As of <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="YAHOO">3.6. How can I make my Yahoo/Hotmail/GMX account work?</H3
+NAME="YAHOO"
+>3.7. How can I make my Yahoo/Hotmail/GMX account work?</A
+></H3
><P
> The default configuration shouldn't impact the usability of any of these services.
It will, however, make all cookies temporary, so that your browser will forget your
><H3
CLASS="SECT2"
><A
-NAME="CONFIGFILES">3.7. What's the difference between the
+NAME="CONFIGFILES"
+>3.8. What's the difference between the
<SPAN
CLASS="QUOTE"
>"Cautious"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Advanced"</SPAN
-> defaults?</H3
+> defaults?</A
+></H3
><P
> Configuring <SPAN
CLASS="APPLICATION"
><DIV
CLASS="TABLE"
><A
-NAME="AEN320"><P
+NAME="AEN328"
+></A
+><P
><B
>Table 1. Default Configurations</B
></P
WIDTH="25%"
ALIGN="LEFT"
VALIGN="TOP"
->no</TD
+>yes</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
><H3
CLASS="SECT2"
><A
-NAME="BROWSECONFIG">3.8. Why can I change the configuration
-with a browser? Does that not raise security issues?</H3
+NAME="BROWSECONFIG"
+>3.9. Why can I change the configuration
+with a browser? Does that not raise security issues?</A
+></H3
><P
> It may seem strange that regular users can edit the config files with their
browsers, although the whole <TT
><H3
CLASS="SECT2"
><A
-NAME="AEN413">3.9. What is the <TT
+NAME="AEN431"
+>3.10. What is the <TT
CLASS="FILENAME"
>default.filter</TT
> file? What is a <SPAN
CLASS="QUOTE"
>"filter"</SPAN
->?</H3
+>?</A
+></H3
><P
> The <A
HREF="../user-manual/filter-file.html"
>default.filter</TT
></A
>
- file is where <SPAN
-CLASS="emphasis"
-><I
+ file is where <I
CLASS="EMPHASIS"
>filters</I
-></SPAN
> are defined, which can be used to modify or
- remove, web page content on the fly. Filters apply to <SPAN
-CLASS="emphasis"
-><I
+ remove, web page content on the fly. Filters apply to <I
CLASS="EMPHASIS"
>anything</I
-></SPAN
>
in the page source, including HTML tags, and JavaScript. Regular expressions are used
to accomplish this. There are a number of pre-defined filters to deal with common
><H3
CLASS="SECT2"
><A
-NAME="AEN429">3.10. How can I set up <SPAN
+NAME="AEN447"
+>3.11. How can I set up <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> to act as a proxy for my
- LAN?</H3
+ LAN?</A
+></H3
><P
> By default, <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN447">3.11. Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</H3
+NAME="AEN465"
+>3.12. Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</A
+></H3
><P
> The replacement for blocked images can be controlled with the <A
HREF="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"
>handle-as-image</A
></TT
>
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>and</I
-></SPAN
> <TT
CLASS="LITERAL"
><A
><H3
CLASS="SECT2"
><A
-NAME="AEN464">3.12. Why would anybody want to see a checkerboard pattern?</H3
+NAME="AEN482"
+>3.13. Why would anybody want to see a checkerboard pattern?</A
+></H3
><P
> Remember that <A
HREF="general.html#WHATSANAD"
decent, but it shows you that and where images were blocked, which can be very
helpful in case some navigation aid or otherwise innocent image was
erraneously blocked. Some people might also enjoy seeing how many banners
- they <SPAN
-CLASS="emphasis"
-><I
+ they <I
CLASS="EMPHASIS"
>don't</I
-></SPAN
> have to see..</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN469">3.13. I see some images being replaced by a text
-instead of the checkerboard image. Why and how do I get rid of this?</H3
+NAME="AEN487"
+>3.14. I see some images being replaced by a text
+instead of the checkerboard image. Why and how do I get rid of this?</A
+></H3
><P
> This happens when the banners are not embedded in the HTML code of the
page itself, but in separate HTML (sub)documents that are loaded into (i)frames
><H3
CLASS="SECT2"
><A
-NAME="SRVANY">3.14. Can <SPAN
+NAME="SRVANY"
+>3.15. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a service
-on Win2K/NT?</H3
+on Win2K/NT?</A
+></H3
><P
> Yes, it can run as a system service using <B
CLASS="COMMAND"
><H3
CLASS="SECT2"
><A
-NAME="OTHERPROXY">3.15. How can I make <SPAN
+NAME="OTHERPROXY"
+>3.16. How can I make <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> work with other
proxies like <SPAN
CLASS="APPLICATION"
>Squid</SPAN
->?</H3
+>?</A
+></H3
><P
> This can be done and is often useful to combine the benefits of
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="TRANSPARENT">3.16. Can <SPAN
+NAME="TRANSPARENT"
+>3.17. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> run as a <SPAN
CLASS="QUOTE"
>"transparent"</SPAN
-> proxy?</H3
+> proxy?</A
+></H3
><P
> No, <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="misc.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Contacting the developers, Bug Reporting and Feature Requests</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="trouble.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONTACT">6. Contacting the developers, Bug Reporting and Feature Requests</H1
+NAME="CONTACT"
+>6. Contacting the developers, Bug Reporting and Feature Requests</A
+></H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT">6.1. Get Support</H2
+NAME="CONTACT-SUPPORT"
+>6.1. Get Support</A
+></H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS">6.2. Report Bugs</H2
+NAME="CONTACT-BUGS"
+>6.2. Report Bugs</A
+></H2
><P
-> Please report all bugs <SPAN
-CLASS="emphasis"
-><I
+> Please report all bugs <I
CLASS="EMPHASIS"
>only</I
-></SPAN
> through our
bug tracker:
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE">6.3. Request New Features</H2
+NAME="CONTACT-FEATURE"
+>6.3. Request New Features</A
+></H2
><P
> You are welcome to submit ideas on new features or other proposals
for improvement through our feature request tracker at
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-ADS">6.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS"
+>6.4. Report Ads or Other Actions-Related Problems</A
+></H2
><P
> Please send feedback on ads that slipped through, innocent images that were blocked,
and any other problems relating to the <TT
TARGET="_top"
>ijbswa-announce</A
>
- list and available from our <A
+ list and available from our the <A
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>files section</A
+> of
+ our <A
HREF="http://sf.net/projects/ijbswa/"
TARGET="_top"
>project page</A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-OTHER">6.5. Other</H2
+NAME="CONTACT-OTHER"
+>6.5. Other</A
+></H2
><P
>For any other issues, feel free to use the mailing lists. Technically interested users
and people who wish to contribute to the project are also welcome on the developers list!
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="trouble.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Copyright, License and History</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT">7. Privoxy Copyright, License and History</H1
+NAME="COPYRIGHT"
+>7. Privoxy Copyright, License and History</A
+></H1
><P
> Copyright © 2001, 2002 by Privoxy Developers <TT
CLASS="EMAIL"
><H2
CLASS="SECT2"
><A
-NAME="AEN802">7.1. License</H2
+NAME="AEN827"
+>7.1. License</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN818">7.2. History</H2
+NAME="AEN843"
+>7.2. History</A
+></H2
><P
> In the beginning, there was the
<A
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
>General Information</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="GENERAL">1. General Information</H1
+NAME="GENERAL"
+>1. General Information</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="NEWJB">1.1. What is this new version of <SPAN
+NAME="NEWJB"
+>1.1. What is this new version of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> In the beginning, there was the
<A
><H3
CLASS="SECT2"
><A
-NAME="AEN45">1.2. Why <SPAN
+NAME="AEN45"
+>1.2. Why <SPAN
CLASS="QUOTE"
>"Privoxy"</SPAN
->? Why a name change at all?</H3
+>? Why a name change at all?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
> is the
<SPAN
CLASS="QUOTE"
->"<SPAN
-CLASS="emphasis"
-><I
+>"<I
CLASS="EMPHASIS"
>Privacy Enhancing Proxy</I
-></SPAN
>"</SPAN
>. Also, its content
modification and junk suppression allow you to browse your
<SPAN
CLASS="QUOTE"
->"<SPAN
-CLASS="emphasis"
-><I
+>"<I
CLASS="EMPHASIS"
>private</I
-></SPAN
> edition"</SPAN
> of the web.</P
><P
><H3
CLASS="SECT2"
><A
-NAME="DIFFERS">1.3. How does <SPAN
+NAME="DIFFERS"
+>1.3. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> differ
from the old <SPAN
CLASS="APPLICATION"
>Junkbuster?</SPAN
+></A
></H3
><P
> <SPAN
><H3
CLASS="SECT2"
><A
-NAME="PROXYMORON">1.4. What is a <SPAN
+NAME="PROXYMORON"
+>1.4. What is a <SPAN
CLASS="QUOTE"
>"proxy"</SPAN
>? How does
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> work?</H3
+> work?</A
+></H3
><P
> A web proxy is a service, based on a software such as <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="WHATSANAD">1.5. How does <SPAN
+NAME="WHATSANAD"
+>1.5. How does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> know what is
-an ad, and what is not?</H3
+an ad, and what is not?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>'s approach to blocking ads is twofold:</P
><P
-> First, there are certain patterns in the <SPAN
-CLASS="emphasis"
-><I
+> First, there are certain patterns in the <I
CLASS="EMPHASIS"
>locations</I
-></SPAN
> (URLs)
of banner images. This applies to both the path (you wouldn't guess how many
web sites serve their banners from a directory called <SPAN
patterns</A
> to sort out and block the requests for banners.</P
><P
-> Second, banners tend to come in certain <SPAN
-CLASS="emphasis"
-><I
+> Second, banners tend to come in certain <I
CLASS="EMPHASIS"
>sizes</I
-></SPAN
>. But you
can't tell the size of an image by its URL without downloading it, and if you
do, it's too late to save bandwidth. Therefore, <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN136">1.6. Can <SPAN
+NAME="AEN136"
+>1.6. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> make mistakes?
-This does not sound very scientific.</H3
+This does not sound very scientific.</A
+></H3
><P
> Actually, it's a black art ;-) And yes, it is always possible to have a broad
rule accidentally block or change something by mistake. There is a good chance
includes tools to help identify these types of situations so they can be
addressed as needed, allowing you to customize your installation.
(<A
-HREF="trouble.html#AEN719"
+HREF="trouble.html#AEN737"
>See the Troubleshooting section below</A
>.)</P
></DIV
><H3
CLASS="SECT2"
><A
-NAME="BROWSERS2">1.7. My browser does the same things as
+NAME="BROWSERS2"
+>1.7. My browser does the same things as
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> at all?</H3
+> at all?</A
+></H3
><P
-> Modern browsers do indeed have <SPAN
-CLASS="emphasis"
-><I
+> Modern browsers do indeed have <I
CLASS="EMPHASIS"
>some</I
-></SPAN
> of the same
functionality as <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="LICENSE">1.8. Is there is a license or fee? What about a
-warranty? Registration?</H3
+NAME="LICENSE"
+>1.8. Is there is a license or fee? What about a
+warranty? Registration?</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
that should be included.
</P
><P
-> There is <SPAN
-CLASS="emphasis"
-><I
+> There is <I
CLASS="EMPHASIS"
>no warranty</I
-></SPAN
> of any kind, expressed, implied or otherwise.
That is something that would cost real money ;-) There is no registration either.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> really is <SPAN
-CLASS="emphasis"
-><I
+> really is <I
CLASS="EMPHASIS"
>free</I
-></SPAN
>
in every respect!
</P
><H3
CLASS="SECT2"
><A
-NAME="JOINTEAM">1.9. I would like to help you, what do I do?</H3
+NAME="JOINTEAM"
+>1.9. I would like to help you, what do I do?</A
+></H3
><DIV
CLASS="SECT3"
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-MONEY">1.9.1. Money Money Money</H4
+NAME="JOINTEAM-MONEY"
+>1.9.1. Money Money Money</A
+></H4
><P
> We, of course, welcome donations and could use money for domain registering,
buying software to test <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-SOFTWARE">1.9.2. Software</H4
+NAME="JOINTEAM-SOFTWARE"
+>1.9.2. Software</A
+></H4
><P
> If you are a vendor of a web-related software like a browser, web server
or proxy, and would like us to ensure that <SPAN
><H4
CLASS="SECT3"
><A
-NAME="JOINTEAM-WORK">1.9.3. You want to work with us?</H4
+NAME="JOINTEAM-WORK"
+>1.9.3. You want to work with us?</A
+></H4
><P
> Well, helping the team is always a good idea. We welcome new developers,
packaging gurus or documentation writers. Simply <A
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Frequently Asked Questions</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="NEXT"
TITLE="General Information"
HREF="general.html"><LINK
><H1
CLASS="TITLE"
><A
-NAME="AEN2">Privoxy Frequently Asked Questions</H1
+NAME="AEN2"
+>Privoxy Frequently Asked Questions</A
+></H1
><P
CLASS="PUBDATE"
> <SUB
><BR></P
><P
CLASS="PUBDATE"
->$Id: faq.sgml,v 1.61.2.2 2002/06/06 02:51:34 hal9 Exp $<BR></P
+>$Id: faq.sgml,v 1.61.2.5 2002/07/26 15:22:58 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"><P
+NAME="AEN9"
+></A
+><P
></P
><P
> This FAQ gives quick answers to frequently asked questions about
><DL
><DT
>3.1. <A
+HREF="configuration.html#GETUPDATES"
+>Where can I get updated Actions Files?</A
+></DT
+><DT
+>3.2. <A
HREF="configuration.html#NEWCONFIG"
>Can I use my old config files?</A
></DT
><DT
-HREF="configuration.html#AEN258"
+HREF="configuration.html#AEN266"
>What is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
> file?</A
></DT
><DT
HREF="configuration.html#ACTIONSS"
>The <SPAN
CLASS="QUOTE"
>.</A
></DT
><DT
-HREF="configuration.html#AEN277"
+HREF="configuration.html#AEN285"
>How are actions files configured? What is the easiest
way to do this?</A
></DT
><DT
-HREF="configuration.html#AEN285"
+HREF="configuration.html#AEN293"
>There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
the differences?</A
></DT
><DT
HREF="configuration.html#YAHOO"
>How can I make my Yahoo/Hotmail/GMX account work?</A
></DT
><DT
HREF="configuration.html#CONFIGFILES"
>What's the difference between the
<SPAN
> defaults?</A
></DT
><DT
HREF="configuration.html#BROWSECONFIG"
>Why can I change the configuration
with a browser? Does that not raise security issues?</A
></DT
><DT
-HREF="configuration.html#AEN413"
+HREF="configuration.html#AEN431"
>What is the <TT
CLASS="FILENAME"
>default.filter</TT
>?</A
></DT
><DT
-HREF="configuration.html#AEN429"
+HREF="configuration.html#AEN447"
>How can I set up <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
LAN?</A
></DT
><DT
-HREF="configuration.html#AEN447"
+HREF="configuration.html#AEN465"
>Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</A
></DT
><DT
-HREF="configuration.html#AEN464"
+HREF="configuration.html#AEN482"
>Why would anybody want to see a checkerboard pattern?</A
></DT
><DT
-HREF="configuration.html#AEN469"
+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
><DT
HREF="configuration.html#SRVANY"
>Can <SPAN
CLASS="APPLICATION"
on Win2K/NT?</A
></DT
><DT
HREF="configuration.html#OTHERPROXY"
>How can I make <SPAN
CLASS="APPLICATION"
>?</A
></DT
><DT
HREF="configuration.html#TRANSPARENT"
>Can <SPAN
CLASS="APPLICATION"
><DL
><DT
>4.1. <A
-HREF="misc.html#AEN505"
+HREF="misc.html#AEN523"
>How much does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.7. <A
-HREF="misc.html#AEN565"
+HREF="misc.html#AEN583"
>Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.8. <A
-HREF="misc.html#AEN576"
+HREF="misc.html#AEN594"
>Might some things break because header information or
content is being altered?</A
></DT
><DT
>4.9. <A
-HREF="misc.html#AEN587"
+HREF="misc.html#AEN605"
>Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.10. <A
-HREF="misc.html#AEN597"
+HREF="misc.html#AEN615"
>What about as a firewall? Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.11. <A
-HREF="misc.html#AEN603"
+HREF="misc.html#AEN621"
>I have large empty spaces / a checkerboard pattern now where
ads used to be. Why?</A
></DT
><DT
>4.12. <A
-HREF="misc.html#AEN608"
+HREF="misc.html#AEN626"
>How can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></DT
><DT
>4.13. <A
-HREF="misc.html#AEN619"
+HREF="misc.html#AEN637"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><DL
><DT
>5.1. <A
-HREF="trouble.html#AEN700"
+HREF="trouble.html#AEN718"
>I just upgraded and am getting <SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
></DT
><DT
>5.2. <A
-HREF="trouble.html#AEN713"
+HREF="trouble.html#AEN731"
>I just added a new rule, but the steenkin ad is
still getting through. How?</A
></DT
><DT
>5.3. <A
-HREF="trouble.html#AEN719"
+HREF="trouble.html#AEN737"
>One of my favorite sites does not work with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, I have to log in
every time I start IE. What gives?</A
></DT
+><DT
+>5.5. <A
+HREF="trouble.html#FTP"
+>I cannot connect to any FTP sites. <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ seems to be blocking me.</A
+></DT
></DL
></DD
><DT
><DL
><DT
>7.1. <A
-HREF="copyright.html#AEN802"
+HREF="copyright.html#AEN827"
>License</A
></DT
><DT
>7.2. <A
-HREF="copyright.html#AEN818"
+HREF="copyright.html#AEN843"
>History</A
></DT
></DL
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="general.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Installation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="general.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION">2. Installation</H1
+NAME="INSTALLATION"
+>2. Installation</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="WHICHBROWSERS">2.1. Which browsers are supported by <SPAN
+NAME="WHICHBROWSERS"
+>2.1. Which browsers are supported by <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> Any browser that can be configured to use a proxy, which
should be virtually all browsers. Direct browser support is not necessary
><H3
CLASS="SECT2"
><A
-NAME="WHICHOS">2.2. Which operating systems are supported?</H3
+NAME="WHICHOS"
+>2.2. Which operating systems are supported?</A
+></H3
><P
> At present, <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="NEWINSTALL">2.3. Can I install
+NAME="NEWINSTALL"
+>2.3. Can I install
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> over <SPAN
CLASS="APPLICATION"
>Junkbuster</SPAN
->?</H3
+>?</A
+></H3
><P
> We recommend you un-install <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN209">2.4. I just installed <SPAN
+NAME="AEN209"
+>2.4. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>. Is there anything
-special I have to do now?</H3
+special I have to do now?</A
+></H3
><P
> All browsers must be told to use <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="LOCALHOST">2.5. What is the proxy address of <SPAN
+NAME="LOCALHOST"
+>2.5. What is the proxy address of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> If you set up the <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN237">2.6. I just installed <SPAN
+NAME="AEN237"
+>2.6. I just installed <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, and nothing is happening.
-All the ads are there. What's wrong?</H3
+All the ads are there. What's wrong?</A
+></H3
><P
> Did you configure your browser to use <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="general.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Miscellaneous</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="trouble.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="MISC">4. Miscellaneous</H1
+NAME="MISC"
+>4. Miscellaneous</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN505">4.1. How much does <SPAN
+NAME="AEN523"
+>4.1. How much does <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> slow my browsing down? This
-has to add extra time to browsing.</H3
+has to add extra time to browsing.</A
+></H3
><P
> It should not slow you down any in real terms, and may actually help
speed things up since ads, banners and other junk are not being displayed.
><H3
CLASS="SECT2"
><A
-NAME="LOADINGTIMES">4.2. I noticed considerable
-delays in page requests compared to the old Junkbuster. What's wrong?</H3
+NAME="LOADINGTIMES"
+>4.2. I noticed considerable
+delays in page requests compared to the old Junkbuster. What's wrong?</A
+></H3
><P
> If you use any <TT
CLASS="LITERAL"
><H3
CLASS="SECT2"
><A
-NAME="CONFIGURL">4.3. What are "http://config.privoxy.org/" and
-"http://p.p/"?</H3
+NAME="CONFIGURL"
+>4.3. What are "http://config.privoxy.org/" and
+"http://p.p/"?</A
+></H3
><P
> <A
HREF="http://config.privoxy.org/"
CLASS="APPLICATION"
>Privoxy</SPAN
> for the request,
- hence it could not be intercepted, and you have accessed the <SPAN
-CLASS="emphasis"
-><I
+ hence it could not be intercepted, and you have accessed the <I
CLASS="EMPHASIS"
>real</I
-></SPAN
>
web site at config.privoxy.org.</P
><P
>Privoxy</SPAN
>, http://example.com/show-proxy-args and http://i.j.b/,
are no longer supported. If you still use such an old version, you should really consider
- upgrading to 2.9.15.</P
+ upgrading to 2.9.16.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="BLOCKLIST">4.4. Do you still maintain the blocklists?</H3
+NAME="BLOCKLIST"
+>4.4. Do you still maintain the blocklists?</A
+></H3
><P
> No. The patterns for blocking now reside (among other things) in the <A
HREF="../user-manual/actions-file.html"
><H3
CLASS="SECT2"
><A
-NAME="NEWADS">4.5. How can I submit new ads?</H3
+NAME="NEWADS"
+>4.5. How can I submit new ads?</A
+></H3
><P
>Yes, absolutely! Please see the <A
HREF="contact.html"
><H3
CLASS="SECT2"
><A
-NAME="IP">4.6. How can I hide my IP address?</H3
+NAME="IP"
+>4.6. How can I hide my IP address?</A
+></H3
><P
> If you run both the browser and the proxy locally, you cannot hide your IP
address with <SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN565">4.7. Can <SPAN
+NAME="AEN583"
+>4.7. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> guarantee I am anonymous?</H3
+> guarantee I am anonymous?</A
+></H3
><P
> No. Your chances of remaining anonymous are greatly improved, but unless you
are an expert on Internet security it would be safest to assume that
CLASS="APPLICATION"
>Privoxy</SPAN
> can remove various information about you,
- and allows <SPAN
-CLASS="emphasis"
-><I
+ and allows <I
CLASS="EMPHASIS"
>you</I
-></SPAN
> more freedom to decide which sites
you can trust, and what details you want to reveal. But it's still possible
that web sites can find out who you are. Here's one way this can happen.</P
><H3
CLASS="SECT2"
><A
-NAME="AEN576">4.8. Might some things break because header information or
-content is being altered?</H3
+NAME="AEN594"
+>4.8. Might some things break because header information or
+content is being altered?</A
+></H3
><P
> Definitely. More and more sites use HTTP header content to decide what to
display and how to display it. There is many ways that this can be handled,
><H3
CLASS="SECT2"
><A
-NAME="AEN587">4.9. Can <SPAN
+NAME="AEN605"
+>4.9. Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> act as a <SPAN
CLASS="QUOTE"
>"caching"</SPAN
> proxy to
-speed up web browsing?</H3
+speed up web browsing?</A
+></H3
><P
> No, it does not have this ability at all. You want something like
<A
><H3
CLASS="SECT2"
><A
-NAME="AEN597">4.10. What about as a firewall? Can <SPAN
+NAME="AEN615"
+>4.10. What about as a firewall? Can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> protect me?</H3
+> protect me?</A
+></H3
><P
> Not in the way you mean, or in the way a true firewall can.
<SPAN
>Privoxy</SPAN
> can help protect your privacy, but not
protect you from intrusion attempts. It is, of course, perfectly possible
- and recommended to use <SPAN
-CLASS="emphasis"
-><I
+ and recommended to use <I
CLASS="EMPHASIS"
>both</I
-></SPAN
>.</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN603">4.11. I have large empty spaces / a checkerboard pattern now where
-ads used to be. Why?</H3
+NAME="AEN621"
+>4.11. I have large empty spaces / a checkerboard pattern now where
+ads used to be. Why?</A
+></H3
><P
> It would be technically possible eliminate the banners in a way that frees
their screen estate in many cases, by doing all banner blocking with filters,
><H3
CLASS="SECT2"
><A
-NAME="AEN608">4.12. How can <SPAN
+NAME="AEN626"
+>4.12. How can <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> filter Secure (HTTPS) URLs?</H3
+> filter Secure (HTTPS) URLs?</A
+></H3
><P
> Since secure HTTP connections are encrypted SSL sessions between your browser
- and the secure site, and are meant to be reliably <SPAN
-CLASS="emphasis"
-><I
+ and the secure site, and are meant to be reliably <I
CLASS="EMPHASIS"
>secure</I
-></SPAN
>,
there is little that <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN619">4.13. <SPAN
+NAME="AEN637"
+>4.13. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> runs as a <SPAN
CLASS="QUOTE"
>"server"</SPAN
>. How
-secure is it? Do I need to take any special precautions?</H3
+secure is it? Do I need to take any special precautions?</A
+></H3
><P
> There are no known exploits that might affect
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="TURNOFF">4.14. How can I temporarily disable <SPAN
+NAME="TURNOFF"
+>4.14. How can I temporarily disable <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->?</H3
+>?</A
+></H3
><P
> The easiest way is to access <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="REALLYOFF">4.15. When <SPAN
+NAME="REALLYOFF"
+>4.15. When <SPAN
CLASS="QUOTE"
>"disabled"</SPAN
> is <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> totally
-out of the picture?</H3
+out of the picture?</A
+></H3
><P
> No, this just means all filtering and actions are disabled.
<SPAN
><H3
CLASS="SECT2"
><A
-NAME="SEEALSO">4.16. Where can I find more information about <SPAN
+NAME="SEEALSO"
+>4.16. Where can I find more information about <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>
-and related issues?</H3
+and related issues?</A
+></H3
><P
> Other references and sites of interest to <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="trouble.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="bottom"
><A
HREF="misc.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="TROUBLE">5. Troubleshooting</H1
+NAME="TROUBLE"
+>5. Troubleshooting</A
+></H1
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN700">5.1. I just upgraded and am getting <SPAN
+NAME="AEN718"
+>5.1. I just upgraded and am getting <SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
>
-with every web page?</H3
+with every web page?</A
+></H3
><P
> Either <SPAN
CLASS="APPLICATION"
><H3
CLASS="SECT2"
><A
-NAME="AEN713">5.2. I just added a new rule, but the steenkin ad is
-still getting through. How?</H3
+NAME="AEN731"
+>5.2. I just added a new rule, but the steenkin ad is
+still getting through. How?</A
+></H3
><P
> If the ad had been displayed before you added its URL, it will probably be
held in the browser's cache for some time, so it will be displayed without
><H3
CLASS="SECT2"
><A
-NAME="AEN719">5.3. One of my favorite sites does not work with <SPAN
+NAME="AEN737"
+>5.3. One of my favorite sites does not work with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>.
-What can I do?</H3
+What can I do?</A
+></H3
><P
> First verify that it is indeed a <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="DUN">5.4. After installing <SPAN
+NAME="DUN"
+>5.4. After installing <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>, I have to log in
-every time I start IE. What gives?</H2
+every time I start IE. What gives?</A
+></H2
><P
> This is a quirk that effects the installation of
<SPAN
><P
>[Thanks to Ray Griffith for this submission.]</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="FTP"
+>5.5. I cannot connect to any FTP sites. <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ seems to be blocking me.</A
+></H2
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> cannot act as a proxy for FTP traffic,
+ so do not configure your browser to use <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
+ </P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="misc.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy - Home Page</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><META
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><META
NAME="KEYWORD"
CONTENT="privoxy"><META
NAME="KEYWORD"
><H1
CLASS="TITLE"
><A
-NAME="AEN2">Privoxy - Home Page</H1
+NAME="AEN2"
+>Privoxy - Home Page</A
+></H1
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN28"><P
+NAME="AEN28"
+></A
+><P
></P
><P
>
Junkbuster</SPAN
> (tm).</P
><P
->
- The most recent release is 2.9.14 (beta).
+> The most recent release is 2.9.16 (beta).
</P
><P
></P
><HR></DIV
><DIV
CLASS="SECT1"
-><H3
+><H2
CLASS="SECT1"
><A
-NAME="DOWNLOAD">Download</H3
+NAME="DOWNLOAD"
+>Download</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H3
+><HR><H2
CLASS="SECT1"
><A
-NAME="DOCS">Documentation</H3
+NAME="DOCS"
+>Documentation</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H3
+><HR><H2
CLASS="SECT1"
><A
-NAME="MOREINFO">More information</H3
+NAME="MOREINFO"
+>More information</A
+></H2
><P
> <P
></P
></DIV
><DIV
CLASS="SECT1"
-><HR><H2
+><HR><H1
CLASS="SECT1"
><A
-NAME="AEN91"></H2
+NAME="AEN91"
+></A
+></H1
><P
><DIV
CLASS="INFORMALTABLE"
><A
-NAME="AEN94"><P
+NAME="AEN94"
+></A
+><P
></P
><TABLE
BORDER="0"
>Actions Files</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Main Configuration File"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="config.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="filter-file.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="ACTIONS-FILE">8. Actions Files</H1
+NAME="ACTIONS-FILE"
+>8. Actions Files</A
+></H1
><P
> The actions files are used to define what actions
<SPAN
>Privoxy's</SPAN
> array of features. So it is
a set of broad rules that should work reasonably well for users everywhere.
- This is the file that the developers are keeping updated, and making
- available to users.
+ This is the file that the developers are keeping updated, and <A
+HREF="installation.html#INSTALLATION-KEEPUPDATED"
+>making available to users</A
+>.
</P
></LI
><LI
CLASS="FILENAME"
>default.action</TT
>. These have increasing levels of
- aggressiveness <SPAN
-CLASS="emphasis"
-><I
+ aggressiveness <I
CLASS="EMPHASIS"
>and have no influence on your browsing unless
you select them explicitly in the editor</I
-></SPAN
>. It is not recommend
to edit this file.
</P
>alias section</A
> at the top of that file.
Then comes the default set of rules which will apply universally to all
- sites and pages (be <SPAN
-CLASS="emphasis"
-><I
+ sites and pages (be <I
CLASS="EMPHASIS"
>very careful</I
-></SPAN
> with using such a
universal set in <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="AEN1584">8.1. Finding the Right Mix</H2
+NAME="AEN1610"
+>8.1. Finding the Right Mix</A
+></H2
><P
> Note that some <A
HREF="actions-file.html#ACTIONS"
><H2
CLASS="SECT2"
><A
-NAME="AEN1591">8.2. How to Edit</H2
+NAME="AEN1617"
+>8.2. How to Edit</A
+></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
><H2
CLASS="SECT2"
><A
-NAME="ACTIONS-APPLY">8.3. How Actions are Applied to URLs</H2
+NAME="ACTIONS-APPLY"
+>8.3. How Actions are Applied to URLs</A
+></H2
><P
> Actions files are divided into sections. There are special sections,
like the <SPAN
>block</A
> }</TT
>, resulting
- in <SPAN
-CLASS="emphasis"
-><I
+ in <I
CLASS="EMPHASIS"
>both</I
-></SPAN
> actions to apply.</P
><P
> You can trace this process for any given URL by visiting <A
><H2
CLASS="SECT2"
><A
-NAME="AF-PATTERNS">8.4. Patterns</H2
+NAME="AF-PATTERNS"
+>8.4. Patterns</A
+></H2
><P
> Generally, a pattern has the form <TT
CLASS="LITERAL"
CLASS="LITERAL"
>/index.html</TT
>, regardless of the domain,
- i.e. on <SPAN
-CLASS="emphasis"
-><I
+ i.e. on <I
CLASS="EMPHASIS"
>any</I
-></SPAN
> web server.
</P
></DD
><H3
CLASS="SECT3"
><A
-NAME="AEN1655">8.4.1. The Domain Pattern</H3
+NAME="AEN1681"
+>8.4.1. The Domain Pattern</A
+></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.
></DT
><DD
><P
-> matches any domain that <SPAN
-CLASS="emphasis"
-><I
+> matches any domain that <I
CLASS="EMPHASIS"
>ENDS</I
-></SPAN
> in
<TT
CLASS="LITERAL"
></DT
><DD
><P
-> matches any domain that <SPAN
-CLASS="emphasis"
-><I
+> matches any domain that <I
CLASS="EMPHASIS"
>STARTS</I
-></SPAN
> with
<TT
CLASS="LITERAL"
></DT
><DD
><P
-> matches any domain that <SPAN
-CLASS="emphasis"
-><I
+> matches any domain that <I
CLASS="EMPHASIS"
>CONTAINS</I
-></SPAN
> <TT
CLASS="LITERAL"
>.example.</TT
<TT
CLASS="LITERAL"
>wwwz.example.com</TT
-> etc., but <SPAN
-CLASS="emphasis"
-><I
+> etc., but <I
CLASS="EMPHASIS"
>not</I
-></SPAN
>
<TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
-NAME="AEN1717">8.4.2. The Path Pattern</H3
+NAME="AEN1743"
+>8.4.2. The Path Pattern</A
+></H3
><P
> <SPAN
CLASS="APPLICATION"
> (regular expression speak
for the beginning of a line).</P
><P
-> Please also note that matching in the path is <SPAN
-CLASS="emphasis"
-><I
+> Please also note that matching in the path is <I
CLASS="EMPHASIS"
>CASE INSENSITIVE</I
-></SPAN
>
by default, but you can switch to case sensitive at any point in the pattern by using the
<SPAN
CLASS="LITERAL"
>PaTtErN</TT
> in
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>exactly</I
-></SPAN
> this capitalization.</P
></DIV
></DIV
><H2
CLASS="SECT2"
><A
-NAME="ACTIONS">8.5. Actions</H2
+NAME="ACTIONS"
+>8.5. Actions</A
+></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
>
Multi-value. These look exactly like parameterized actions,
but they behave differently: If the action applies multiple times to the
- same URL, but with different parameters, <SPAN
-CLASS="emphasis"
-><I
+ same URL, but with different parameters, <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> the parameters
- from <SPAN
-CLASS="emphasis"
-><I
+ from <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> matches are remembered. This is used for actions
that can be executed for the same request repeatedly, like adding multiple
headers, or filtering through multiple filters. Syntax:
><H4
CLASS="SECT3"
><A
-NAME="ADD-HEADER">8.5.1. add-header</H4
+NAME="ADD-HEADER"
+>8.5.1. add-header</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="BLOCK">8.5.2. block</H4
+NAME="BLOCK"
+>8.5.2. block</A
+></H4
><P
></P
><DIV
</P
><P
>
- A very important exception occurs if <SPAN
-CLASS="emphasis"
-><I
+ A very important exception occurs if <I
CLASS="EMPHASIS"
>both</I
-></SPAN
>
<TT
CLASS="LITERAL"
><H4
CLASS="SECT3"
><A
-NAME="CRUNCH-INCOMING-COOKIES">8.5.3. crunch-incoming-cookies</H4
+NAME="CRUNCH-INCOMING-COOKIES"
+>8.5.3. crunch-incoming-cookies</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> This action is only concerned with <SPAN
-CLASS="emphasis"
-><I
+> This action is only concerned with <I
CLASS="EMPHASIS"
>incoming</I
-></SPAN
> cookies. For
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>outgoing</I
-></SPAN
> cookies, use
<TT
CLASS="LITERAL"
>crunch-outgoing-cookies</A
></TT
>.
- Use <SPAN
-CLASS="emphasis"
-><I
+ Use <I
CLASS="EMPHASIS"
>both</I
-></SPAN
> to disable cookies completely.
</P
><P
-> It makes <SPAN
-CLASS="emphasis"
-><I
+> It makes <I
CLASS="EMPHASIS"
>no sense at all</I
-></SPAN
> to use this action in conjunction
with the <TT
CLASS="LITERAL"
><H4
CLASS="SECT3"
><A
-NAME="CRUNCH-OUTGOING-COOKIES">8.5.4. crunch-outgoing-cookies</H4
+NAME="CRUNCH-OUTGOING-COOKIES"
+>8.5.4. crunch-outgoing-cookies</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> This action is only concerned with <SPAN
-CLASS="emphasis"
-><I
+> This action is only concerned with <I
CLASS="EMPHASIS"
>outgoing</I
-></SPAN
> cookies. For
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>incoming</I
-></SPAN
> cookies, use
<TT
CLASS="LITERAL"
>crunch-incoming-cookies</A
></TT
>.
- Use <SPAN
-CLASS="emphasis"
-><I
+ Use <I
CLASS="EMPHASIS"
>both</I
-></SPAN
> to disable cookies completely.
</P
><P
-> It makes <SPAN
-CLASS="emphasis"
-><I
+> It makes <I
CLASS="EMPHASIS"
>no sense at all</I
-></SPAN
> to use this action in conjunction
with the <TT
CLASS="LITERAL"
><H4
CLASS="SECT3"
><A
-NAME="DEANIMATE-GIFS">8.5.5. deanimate-gifs</H4
+NAME="DEANIMATE-GIFS"
+>8.5.5. deanimate-gifs</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="DOWNGRADE-HTTP-VERSION">8.5.6. downgrade-http-version</H4
+NAME="DOWNGRADE-HTTP-VERSION"
+>8.5.6. downgrade-http-version</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="FAST-REDIRECTS">8.5.7. fast-redirects</H4
+NAME="FAST-REDIRECTS"
+>8.5.7. fast-redirects</A
+></H4
><P
></P
><DIV
will link to some script on their own servers, giving the destination as a
parameter, which will then redirect you to the final target. URLs
resulting from this scheme typically look like:
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>http://some.place/click-tracker.cgi?target=http://some.where.else</I
-></SPAN
>.
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="FILTER">8.5.8. filter</H4
+NAME="FILTER"
+>8.5.8. filter</A
+></H4
><P
></P
><DIV
><TD
><PRE
CLASS="SCREEN"
->+filter{banners-by-size} # Kill banners based on their size for this page (<SPAN
-CLASS="emphasis"
-><I
+>+filter{banners-by-size} # Kill banners based on their size for this page (<I
CLASS="EMPHASIS"
>very</I
-></SPAN
> efficient!)</PRE
></TD
></TR
</P
><P
> <A
+NAME="FILTER-BANNERS-BY-LINK"
+></A
+>
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>+filter{banners-by-link} # Kill banners based on the link they are contained in (experimental)</PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> <A
+NAME="FILTER-IMG-REORDER"
+></A
+>
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>+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-CONTENT-COOKIES"
></A
>
></TD
></TR
></TABLE
+>
+ </P
+><P
+> <A
+NAME="FILTER-JS-EVENTS"
+></A
+>
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>+filter{js-events} # Kill all JS event bindings (<I
+CLASS="EMPHASIS"
+>Radically destructive!</I
+> Only for extra nasty sites) </PRE
+></TD
+></TR
+></TABLE
>
</P
></DD
><H4
CLASS="SECT3"
><A
-NAME="HANDLE-AS-IMAGE">8.5.9. handle-as-image</H4
+NAME="HANDLE-AS-IMAGE"
+>8.5.9. handle-as-image</A
+></H4
><P
></P
><DIV
>Typical use:</DT
><DD
><P
->Mark URLs as belonging to images (so they'll be replaced by images <SPAN
-CLASS="emphasis"
-><I
+>Mark URLs as belonging to images (so they'll be replaced by images <I
CLASS="EMPHASIS"
>if they get blocked</I
-></SPAN
>)</P
></DD
><DT
HREF="actions-file.html#BLOCK"
>block</A
></TT
-> action <SPAN
-CLASS="emphasis"
-><I
+> action <I
CLASS="EMPHASIS"
>also applies</I
-></SPAN
>,
the presence or absence of this mark decides whether an HTML <SPAN
CLASS="QUOTE"
><H4
CLASS="SECT3"
><A
-NAME="HIDE-FORWARDED-FOR-HEADERS">8.5.10. hide-forwarded-for-headers</H4
+NAME="HIDE-FORWARDED-FOR-HEADERS"
+>8.5.10. hide-forwarded-for-headers</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="HIDE-FROM-HEADER">8.5.11. hide-from-header</H4
+NAME="HIDE-FROM-HEADER"
+>8.5.11. hide-from-header</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="HIDE-REFERRER">8.5.12. hide-referrer</H4
+NAME="HIDE-REFERRER"
+>8.5.12. hide-referrer</A
+></H4
><A
NAME="HIDE-REFERER"
></A
> is the preferred option here, since some servers will
not send images back otherwise, in an attempt to prevent their valuable
content from being embedded elsewhere (and hence, without being surrounded
- by <SPAN
-CLASS="emphasis"
-><I
+ by <I
CLASS="EMPHASIS"
>their</I
-></SPAN
> banners).
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="HIDE-USER-AGENT">8.5.13. hide-user-agent</H4
+NAME="HIDE-USER-AGENT"
+>8.5.13. hide-user-agent</A
+></H4
><P
></P
><DIV
><P
> This breaks many web sites that depend on looking at this header in order
to customize their content for different browsers (which, by the
- way, is <SPAN
-CLASS="emphasis"
-><I
+ way, is <I
CLASS="EMPHASIS"
>NOT</I
-></SPAN
> a <A
HREF="http://www.javascriptkit.com/javaindex.shtml"
TARGET="_top"
CLASS="APPLICATION"
>Privoxy</SPAN
> is
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>not recommended</I
-></SPAN
>. In single-user, single-browser
setups, you might use it to delete your OS version information from
the headers, because it is an invitation to exploit known bugs for your
><H4
CLASS="SECT3"
><A
-NAME="KILL-POPUPS">8.5.14. kill-popups<A
+NAME="KILL-POPUPS"
+>8.5.14. kill-popups<A
NAME="KILL-POPUP"
></A
+></A
></H4
><P
></P
>Privoxy</SPAN
>.
If the only kind of pop-ups that you want to kill are exit consoles (those
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>really nasty</I
-></SPAN
> windows that appear when you close an other
one), you might want to use
<TT
><H4
CLASS="SECT3"
><A
-NAME="LIMIT-CONNECT">8.5.15. limit-connect</H4
+NAME="LIMIT-CONNECT"
+>8.5.15. limit-connect</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="PREVENT-COMPRESSION">8.5.16. prevent-compression</H4
+NAME="PREVENT-COMPRESSION"
+>8.5.16. prevent-compression</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SEND-VANILLA-WAFER">8.5.17. send-vanilla-wafer</H4
+NAME="SEND-VANILLA-WAFER"
+>8.5.17. send-vanilla-wafer</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SEND-WAFER">8.5.18. send-wafer</H4
+NAME="SEND-WAFER"
+>8.5.18. send-wafer</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="SESSION-COOKIES-ONLY">8.5.19. session-cookies-only</H4
+NAME="SESSION-COOKIES-ONLY"
+>8.5.19. session-cookies-only</A
+></H4
><P
></P
><DIV
> Allow only temporary <SPAN
CLASS="QUOTE"
>"session"</SPAN
-> cookies (for the current browser session <SPAN
-CLASS="emphasis"
-><I
+> cookies (for the current browser session <I
CLASS="EMPHASIS"
>only</I
-></SPAN
>).
</P
></DD
sites, and is the recommended setting.
</P
><P
-> It makes <SPAN
-CLASS="emphasis"
-><I
+> It makes <I
CLASS="EMPHASIS"
>no sense at all</I
-></SPAN
> to use <TT
CLASS="LITERAL"
>session-cookies-only</TT
><H4
CLASS="SECT3"
><A
-NAME="SET-IMAGE-BLOCKER">8.5.20. set-image-blocker</H4
+NAME="SET-IMAGE-BLOCKER"
+>8.5.20. set-image-blocker</A
+></H4
><P
></P
><DIV
>Effect:</DT
><DD
><P
-> This action alone doesn't do anything noticeable. If <SPAN
-CLASS="emphasis"
-><I
+> This action alone doesn't do anything noticeable. If <I
CLASS="EMPHASIS"
>both</I
-></SPAN
>
<TT
CLASS="LITERAL"
HREF="actions-file.html#BLOCK"
>block</A
></TT
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>and</I
-></SPAN
> <TT
CLASS="LITERAL"
><A
HREF="actions-file.html#HANDLE-AS-IMAGE"
>handle-as-image</A
></TT
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>also</I
-></SPAN
>
apply, i.e. if the request is to be blocked as an image,
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>then</I
-></SPAN
> the parameter of this action decides what will be
sent as a replacement.
</P
> There is a third (advanced) type, called <SPAN
CLASS="QUOTE"
>"auto"</SPAN
->. It is <SPAN
-CLASS="emphasis"
-><I
+>. It is <I
CLASS="EMPHASIS"
>NOT</I
-></SPAN
> to be
used in <TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
-NAME="AEN2635">8.5.21. Summary</H3
+NAME="AEN2671"
+>8.5.21. Summary</A
+></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">8.6. Aliases</H2
+NAME="ALIASES"
+>8.6. Aliases</A
+></H2
><P
> Custom <SPAN
CLASS="QUOTE"
> and <SPAN
CLASS="QUOTE"
>"}"</SPAN
->, but we <SPAN
-CLASS="emphasis"
-><I
+>, but we <I
CLASS="EMPHASIS"
>strongly
recommend</I
-></SPAN
> that you only use <SPAN
CLASS="QUOTE"
>"a"</SPAN
> sign, since they are merely textually
expanded.</P
><P
-> Aliases can be used throughout the actions file, but they <SPAN
-CLASS="emphasis"
-><I
+> Aliases can be used throughout the actions file, but they <I
CLASS="EMPHASIS"
>must be
defined in a special section at the top of the file!</I
-></SPAN
>
And there can only be one such section per actions file. Each actions file may
have its own alias section, and the aliases defined in it are only visible
CLASS="QUOTE"
>"shop"</SPAN
>, you can later change your policy on shops in
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>one</I
-></SPAN
> place, and your changes will take effect everywhere
in the actions file where the <SPAN
CLASS="QUOTE"
><H2
CLASS="SECT2"
><A
-NAME="ACT-EXAMPLES">8.7. Actions Files Tutorial</H2
+NAME="ACT-EXAMPLES"
+>8.7. Actions Files Tutorial</A
+></H2
><P
> The above chapters have shown <A
HREF="actions-file.html"
><H3
CLASS="SECT3"
><A
-NAME="AEN2687">8.7.1. default.action</H3
+NAME="AEN2723"
+>8.7.1. default.action</A
+></H3
><P
>Every config file should start with a short comment stating its purpose:</P
><P
></P
><P
> Now come the regular sections, i.e. sets of actions, accompanied
- by URL patterns to which they apply. Remember <SPAN
-CLASS="emphasis"
-><I
+ by URL patterns to which they apply. Remember <I
CLASS="EMPHASIS"
>all actions
are disabled when matching starts</I
-></SPAN
>, so we have to explicitly
enable the ones we want.</P
><P
set of actions used in this <SPAN
CLASS="QUOTE"
>"default"</SPAN
-> section <SPAN
-CLASS="emphasis"
-><I
+> section <I
CLASS="EMPHASIS"
>will
be applied to all requests as a start</I
-></SPAN
>. It can be partly or
wholly overridden by later matches further down this file, or in user.action,
but it will still be largely responsible for your overall browsing
+<A
HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
>filter{banners-by-size}</A
+> \
+ -<A
+HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
+>filter{banners-by-link}</A
+> \
+ -<A
+HREF="actions-file.html#FILTER-IMG-REORDER"
+>filter{img-reorder}</A
> \
-<A
HREF="actions-file.html#FILTER-SHOCKWAVE-FLASH"
-<A
HREF="actions-file.html#FILTER-CRUDE-PARENTAL"
>filter{crude-parental}</A
+> \
+ -<A
+HREF="actions-file.html#FILTER-JS-EVENTS"
+>filter{js-events}</A
> \
-<A
HREF="actions-file.html#HANDLE-AS-IMAGE"
>"general policy"</SPAN
> that applies
universally and won't get any exceptions defined later. Other choices,
- like not blocking (which is <SPAN
-CLASS="emphasis"
-><I
+ like not blocking (which is <I
CLASS="EMPHASIS"
>understandably</I
-></SPAN
> the
default!) need exceptions, i.e. we need to specify explicitly what we
want to block in later sections.
CLASS="APPLICATION"
>Privoxy</SPAN
> knows which
- URLs belong to images, so that <SPAN
-CLASS="emphasis"
-><I
+ URLs belong to images, so that <I
CLASS="EMPHASIS"
>if</I
-></SPAN
> they are to
be blocked, a substitute image can be sent, rather than an HTML page.
Contacting the remote site to find out is not an option, since it
would destroy the loading time advantage of banner blocking, and it
- would feed the advertisers (in terms of money <SPAN
-CLASS="emphasis"
-><I
+ would feed the advertisers (in terms of money <I
CLASS="EMPHASIS"
>and</I
-></SPAN
>
information). We can mark any URL as an image with the <TT
CLASS="LITERAL"
><P
> And then there are known banner sources. They often use scripts to
generate the banners, so it won't be visible from the URL that the
- request is for an image. Hence we block them <SPAN
-CLASS="emphasis"
-><I
+ request is for an image. Hence we block them <I
CLASS="EMPHASIS"
>and</I
-></SPAN
>
mark them as images in one go, with the help of our
<TT
> e.g. catches
<SPAN
CLASS="QUOTE"
->"nasty-<SPAN
-CLASS="emphasis"
-><I
+>"nasty-<I
CLASS="EMPHASIS"
>ads</I
-></SPAN
>.nasty-corp.com"</SPAN
> as intended,
but also <SPAN
CLASS="QUOTE"
->"downlo<SPAN
-CLASS="emphasis"
-><I
+>"downlo<I
CLASS="EMPHASIS"
>ads</I
-></SPAN
>.sourcefroge.net"</SPAN
> or
<SPAN
CLASS="QUOTE"
->"<SPAN
-CLASS="emphasis"
-><I
+>"<I
CLASS="EMPHASIS"
>ads</I
-></SPAN
>l.some-provider.net."</SPAN
> So here come some
well-known exceptions to the <TT
>-block</A
></TT
>
- applies, so (unless it matches <SPAN
-CLASS="emphasis"
-><I
+ applies, so (unless it matches <I
CLASS="EMPHASIS"
>again</I
-></SPAN
> further down) it ends up
with no <TT
CLASS="LITERAL"
>filter</A
></TT
>
- disables <SPAN
-CLASS="emphasis"
-><I
+ disables <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> filters in one fell swoop!</P
><P
> <TABLE
><H3
CLASS="SECT3"
><A
-NAME="AEN2841">8.7.2. user.action</H3
+NAME="AEN2880"
+>8.7.2. user.action</A
+></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,
CLASS="FILENAME"
>user.action</TT
> is also a
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>safe</I
-></SPAN
> place for your personal settings, since
<TT
CLASS="FILENAME"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="config.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="filter-file.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Appendix</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="See Also"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="seealso.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
><H1
CLASS="SECT1"
><A
-NAME="APPENDIX">14. Appendix</H1
+NAME="APPENDIX"
+>14. Appendix</A
+></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="REGEX">14.1. Regular Expressions</H2
+NAME="REGEX"
+>14.1. Regular Expressions</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>.</I
-></SPAN
> - Matches any single character, e.g. <SPAN
CLASS="QUOTE"
>"a"</SPAN
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>?</I
-></SPAN
> - The preceding character or expression is matched ZERO or ONE
times. Either/or.
</TD
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>+</I
-></SPAN
> - The preceding character or expression is matched ONE or MORE
times.
</TD
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>*</I
-></SPAN
> - The preceding character or expression is matched ZERO or MORE
times.
</TD
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>\</I
-></SPAN
> - The <SPAN
CLASS="QUOTE"
>"escape"</SPAN
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>[]</I
-></SPAN
> - Characters enclosed in brackets will be matched if
any of the enclosed characters are encountered. For instance, <SPAN
CLASS="QUOTE"
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>()</I
-></SPAN
> - parentheses are used to group a sub-expression,
or multiple sub-expressions.
</TD
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>|</I
-></SPAN
> - The <SPAN
CLASS="QUOTE"
>"bar"</SPAN
list. This is enough to get us started with a few simple examples which may
be more illuminating:</P
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
><TT
CLASS="LITERAL"
>/.*/banners/.*</TT
></I
-></SPAN
> - A simple example
that uses the common combination of <SPAN
CLASS="QUOTE"
><P
> A now something a little more complex:</P
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
><TT
CLASS="LITERAL"
>/.*/adv((er)?ts?|ertis(ing|ements?))?/</TT
></I
-></SPAN
> -
We have several literal forward slashes again (<SPAN
CLASS="QUOTE"
CLASS="QUOTE"
>".*"</SPAN
>, so we are matching against any conceivable sub-path, just so
- it matches our expression. The only true literal that <SPAN
-CLASS="emphasis"
-><I
+ it matches our expression. The only true literal that <I
CLASS="EMPHASIS"
>must
match</I
-></SPAN
> our pattern is <SPAN
CLASS="APPLICATION"
>adv</SPAN
CLASS="QUOTE"
>"ing"</SPAN
>
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>OR</I
-></SPAN
> <SPAN
CLASS="QUOTE"
>"ements?"</SPAN
>, which would then match
either spelling.</P
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
><TT
CLASS="LITERAL"
>/.*/advert[0-9]+\.(gif|jpe?g)</TT
></I
-></SPAN
> - Again
another path statement with forward slashes. Anything in the square brackets
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="AEN3388">14.2. <SPAN
+NAME="AEN3435"
+>14.2. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->'s Internal Pages</H2
+>'s Internal Pages</A
+></H2
><P
> Since <SPAN
CLASS="APPLICATION"
Privoxy main page:
</P
><A
-NAME="AEN3403"><BLOCKQUOTE
+NAME="AEN3450"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
editing of actions files:
</P
><A
-NAME="AEN3411"><BLOCKQUOTE
+NAME="AEN3458"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show the source code version numbers:
</P
><A
-NAME="AEN3416"><BLOCKQUOTE
+NAME="AEN3463"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show the browser's request headers:
</P
><A
-NAME="AEN3421"><BLOCKQUOTE
+NAME="AEN3468"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN3426"><BLOCKQUOTE
+NAME="AEN3473"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN3432"><BLOCKQUOTE
+NAME="AEN3479"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN3436"><BLOCKQUOTE
+NAME="AEN3483"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
</P
></BLOCKQUOTE
><A
-NAME="AEN3439"><BLOCKQUOTE
+NAME="AEN3486"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>
><H3
CLASS="SECT3"
><A
-NAME="BOOKMARKLETS">14.2.1. Bookmarklets</H3
+NAME="BOOKMARKLETS"
+>14.2.1. Bookmarklets</A
+></H3
><P
> Below are some <SPAN
CLASS="QUOTE"
><H2
CLASS="SECT2"
><A
-NAME="CHAIN">14.3. Chain of Events</H2
+NAME="CHAIN"
+>14.3. Chain of Events</A
+></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">14.4. Anatomy of an Action</H2
+NAME="ACTIONSANAT"
+>14.4. Anatomy of an Action</A
+></H2
><P
> The way <SPAN
CLASS="APPLICATION"
>
to any given URL can be complex, and not always so
easy to understand what is happening. And sometimes we need to be able to
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>see</I
-></SPAN
> just what <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
></A
>
(i.e. not persistent). So we will allow persistent cookies for google. The
- second turns <SPAN
-CLASS="emphasis"
-><I
+ second turns <I
CLASS="EMPHASIS"
>off</I
-></SPAN
> any
<A
HREF="actions-file.html#FAST-REDIRECTS"
>"+block"</SPAN
></A
>
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>and</I
-></SPAN
> an
<A
HREF="actions-file.html#HANDLE-AS-IMAGE"
>"/ads"</SPAN
>! But
we did not want this at all! Now we see why we get the blank page. We could
- now add a new action below this that explicitly does <SPAN
-CLASS="emphasis"
-><I
+ now add a new action below this that explicitly does <I
CLASS="EMPHASIS"
>not</I
-></SPAN
>
block (<SPAN
CLASS="QUOTE"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="seealso.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
>The Main Configuration File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="actions-file.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONFIG">7. The Main Configuration File</H1
+NAME="CONFIG"
+>7. The Main Configuration File</A
+></H1
><P
> Again, the main configuration file is named <TT
CLASS="FILENAME"
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>confdir /etc/privoxy</I
-></SPAN
></P
>
</TT
><H2
CLASS="SECT2"
><A
-NAME="CONF-LOG-LOC">7.1. Configuration and Log File Locations</H2
+NAME="CONF-LOG-LOC"
+>7.1. Configuration and Log File Locations</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="CONFDIR">7.1.1. confdir</H4
+NAME="CONFDIR"
+>7.1.1. confdir</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
->/etc/privoxy (Unix) <SPAN
-CLASS="emphasis"
-><I
+>/etc/privoxy (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>Effect if unset:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Mandatory</I
-></SPAN
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="LOGDIR">7.1.2. logdir</H4
+NAME="LOGDIR"
+>7.1.2. logdir</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
->/var/log/privoxy (Unix) <SPAN
-CLASS="emphasis"
-><I
+>/var/log/privoxy (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>Effect if unset:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Mandatory</I
-></SPAN
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="ACTIONSFILE">7.1.3. actionsfile</H4
+NAME="ACTIONSFILE"
+>7.1.3. actionsfile</A
+></H4
><A
NAME="DEFAULT.ACTION"
></A
><H4
CLASS="SECT3"
><A
-NAME="FILTERFILE">7.1.4. filterfile</H4
+NAME="FILTERFILE"
+>7.1.4. filterfile</A
+></H4
><A
NAME="DEFAULT.FILTER"
></A
>Default value:</DT
><DD
><P
->default.filter (Unix) <SPAN
-CLASS="emphasis"
-><I
+>default.filter (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> default.filter.txt (Windows)</P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="LOGFILE">7.1.5. logfile</H4
+NAME="LOGFILE"
+>7.1.5. logfile</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
->logfile (Unix) <SPAN
-CLASS="emphasis"
-><I
+>logfile (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> privoxy.log (Windows)</P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="JARFILE">7.1.6. jarfile</H4
+NAME="JARFILE"
+>7.1.6. jarfile</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
->jarfile (Unix) <SPAN
-CLASS="emphasis"
-><I
+>jarfile (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> privoxy.jar (Windows)</P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="TRUSTFILE">7.1.7. trustfile</H4
+NAME="TRUSTFILE"
+>7.1.7. trustfile</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset (commented out)</I
-></SPAN
->. When activated: trust (Unix) <SPAN
-CLASS="emphasis"
-><I
+>. When activated: trust (Unix) <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> trust.txt (Windows)</P
></DD
><DT
><DD
><P
> The trust mechanism is an experimental feature for building white-lists and should
- be used with care. It is <SPAN
-CLASS="emphasis"
-><I
+ be used with care. It is <I
CLASS="EMPHASIS"
>NOT</I
-></SPAN
> recommended for the casual user.
</P
><P
><H2
CLASS="SECT2"
><A
-NAME="LOCAL-SET-UP">7.2. Local Set-up Documentation</H2
+NAME="LOCAL-SET-UP"
+>7.2. Local Set-up Documentation</A
+></H2
><P
> If you intend to operate <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="USER-MANUAL">7.2.1. user-manual</H4
+NAME="USER-MANUAL"
+>7.2.1. user-manual</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><TD
><PRE
CLASS="SCREEN"
->user-manual file:///usr/share/doc/privoxy-2.9.15/user-manual/</PRE
+>user-manual file:///usr/share/doc/privoxy-2.9.16/user-manual/</PRE
></TD
></TR
></TABLE
><TD
ALIGN="LEFT"
><P
-> If set, this option should be <SPAN
-CLASS="emphasis"
-><I
+> If set, this option should be <I
CLASS="EMPHASIS"
>the first option in the config
file</I
-></SPAN
>, because it is used while the config file is being read.
</P
></TD
><H4
CLASS="SECT3"
><A
-NAME="TRUST-INFO-URL">7.2.2. trust-info-url</H4
+NAME="TRUST-INFO-URL"
+>7.2.2. trust-info-url</A
+></H4
><P
></P
><DIV
> The value of this option only matters if the experimental trust mechanism has been
activated. (See <A
HREF="config.html#TRUSTFILE"
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>trustfile</I
-></SPAN
></A
> above.)
</P
><H4
CLASS="SECT3"
><A
-NAME="ADMIN-ADDRESS">7.2.3. admin-address</H4
+NAME="ADMIN-ADDRESS"
+>7.2.3. admin-address</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="PROXY-INFO-URL">7.2.4. proxy-info-url</H4
+NAME="PROXY-INFO-URL"
+>7.2.4. proxy-info-url</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><H2
CLASS="SECT2"
><A
-NAME="DEBUGGING">7.3. Debugging</H2
+NAME="DEBUGGING"
+>7.3. Debugging</A
+></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">7.3.1. debug</H4
+NAME="DEBUG"
+>7.3.1. debug</A
+></H4
><P
></P
><DIV
> Key values that determine what information gets logged to the
<A
HREF="config.html#LOGFILE"
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>logfile</I
-></SPAN
></A
>.
</P
</P
><P
> A debug level of 1 is informative because it will show you each request
- as it happens. <SPAN
-CLASS="emphasis"
-><I
+ as it happens. <I
CLASS="EMPHASIS"
>1, 4096 and 8192 are highly recommended</I
-></SPAN
>
so that you will notice when things go wrong. The other levels are probably
only of interest if you are hunting down a specific problem. They can produce
</P
><P
-> The reporting of <SPAN
-CLASS="emphasis"
-><I
+> The reporting of <I
CLASS="EMPHASIS"
>fatal</I
-></SPAN
> errors (i.e. ones which crash
<SPAN
CLASS="APPLICATION"
CLASS="QUOTE"
>"debug
512"</SPAN
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>ONLY</I
-></SPAN
> and not enable anything else.
</P
></DD
><H4
CLASS="SECT3"
><A
-NAME="SINGLE-THREADED">7.3.2. single-threaded</H4
+NAME="SINGLE-THREADED"
+>7.3.2. single-threaded</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>None</I
-></SPAN
></P
></DD
><DT
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><DD
><P
> This option is only there for debug purposes and you should never
- need to use it. <SPAN
-CLASS="emphasis"
-><I
+ need to use it. <I
CLASS="EMPHASIS"
>It will drastically reduce performance.</I
-></SPAN
>
</P
></DD
><H2
CLASS="SECT2"
><A
-NAME="ACCESS-CONTROL">7.4. Access Control and Security</H2
+NAME="ACCESS-CONTROL"
+>7.4. Access Control and Security</A
+></H2
><P
> This section of the config file controls the security-relevant aspects
of <SPAN
><H4
CLASS="SECT3"
><A
-NAME="LISTEN-ADDRESS">7.4.1. listen-address</H4
+NAME="LISTEN-ADDRESS"
+>7.4.1. listen-address</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="TOGGLE">7.4.2. toggle</H4
+NAME="TOGGLE"
+>7.4.2. toggle</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</H4
+NAME="ENABLE-REMOTE-TOGGLE"
+>7.4.3. enable-remote-toggle</A
+></H4
><P
></P
><DIV
any URL.
</P
><P
-> For the time being, access to the toggle feature can <SPAN
-CLASS="emphasis"
-><I
+> For the time being, access to the toggle feature can <I
CLASS="EMPHASIS"
>not</I
-></SPAN
> be
controlled separately by <SPAN
CLASS="QUOTE"
CLASS="LITERAL"
>listen-address</TT
> above) can
- toggle it for all users. So this option is <SPAN
-CLASS="emphasis"
-><I
+ toggle it for all users. So this option is <I
CLASS="EMPHASIS"
>not recommended</I
-></SPAN
>
for multi-user environments with untrusted users.
</P
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-EDIT-ACTIONS">7.4.4. enable-edit-actions</H4
+NAME="ENABLE-EDIT-ACTIONS"
+>7.4.4. enable-edit-actions</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> For the time being, access to the editor can <SPAN
-CLASS="emphasis"
-><I
+> For the time being, access to the editor can <I
CLASS="EMPHASIS"
>not</I
-></SPAN
> be
controlled separately by <SPAN
CLASS="QUOTE"
CLASS="LITERAL"
>listen-address</TT
> above) can
- modify its configuration for all users. So this option is <SPAN
-CLASS="emphasis"
-><I
+ modify its configuration for all users. So this option is <I
CLASS="EMPHASIS"
>not
recommended</I
-></SPAN
> for multi-user environments with untrusted users.
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="ACLS">7.4.5. ACLs: permit-access and deny-access</H4
+NAME="ACLS"
+>7.4.5. ACLs: permit-access and deny-access</A
+></H4
><A
NAME="PERMIT-ACCESS"
></A
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><DD
><P
> Access controls are included at the request of ISPs and systems
- administrators, and <SPAN
-CLASS="emphasis"
-><I
+ administrators, and <I
CLASS="EMPHASIS"
>are not usually needed by individual users</I
-></SPAN
>.
For a typical home user, it will normally suffice to ensure that
<SPAN
(127.0.0.1) or internal (home) network address by means of the
<A
HREF="config.html#LISTEN-ADDRESS"
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>listen-address</I
-></SPAN
></A
>
option.
>dst_addr</I
></TT
>
- that is examined is the address of the forwarder and <SPAN
-CLASS="emphasis"
-><I
+ that is examined is the address of the forwarder and <I
CLASS="EMPHASIS"
>NOT</I
-></SPAN
> the address
of the ultimate target. This is necessary because it may be impossible for the local
<SPAN
</P
><P
> You should prefer using IP addresses over DNS names, because the address lookups take
- time. All DNS names must resolve! You can <SPAN
-CLASS="emphasis"
-><I
+ time. All DNS names must resolve! You can <I
CLASS="EMPHASIS"
>not</I
-></SPAN
> use domain patterns
like <SPAN
CLASS="QUOTE"
>dst_addr</I
></TT
> implies that
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> destination addresses are OK:
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="BUFFER-LIMIT">7.4.6. buffer-limit</H4
+NAME="BUFFER-LIMIT"
+>7.4.6. buffer-limit</A
+></H4
><P
></P
><DIV
CLASS="LITERAL"
>buffer-limit</TT
> Kbytes
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>each</I
-></SPAN
>, unless you have enabled <SPAN
CLASS="QUOTE"
>"single-threaded"</SPAN
><H2
CLASS="SECT2"
><A
-NAME="FORWARDING">7.5. Forwarding</H2
+NAME="FORWARDING"
+>7.5. Forwarding</A
+></H2
><P
> This feature allows routing of HTTP requests through a chain of
multiple proxies.
><H4
CLASS="SECT3"
><A
-NAME="FORWARD">7.5.1. forward</H4
+NAME="FORWARD"
+>7.5.1. forward</A
+></H4
><P
></P
><DIV
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="SOCKS">7.5.2. forward-socks4 and forward-socks4a</H4
+NAME="SOCKS"
+>7.5.2. forward-socks4 and forward-socks4a</A
+></H4
><A
NAME="FORWARD-SOCKS4"
></A
>Default value:</DT
><DD
><P
-><SPAN
-CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Unset</I
-></SPAN
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding Examples</H4
+NAME="ADVANCED-FORWARDING-EXAMPLES"
+>7.5.3. Advanced Forwarding Examples</A
+></H4
><P
> If you have links to multiple ISPs that provide various special content
only to their subscribers, you can configure multiple <SPAN
>Privoxies</SPAN
>
which have connections to the respective ISPs to act as forwarders to each other, so that
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>your</I
-></SPAN
> users can see the internal content of all ISPs.</P
><P
> Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
><H2
CLASS="SECT2"
><A
-NAME="WINDOWS-GUI">7.6. Windows GUI Options</H2
+NAME="WINDOWS-GUI"
+>7.6. Windows GUI Options</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>activity-animation 1</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-messages 1</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-buffer-size 1</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-max-lines 200</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-highlight-messages 1</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-font-name Comic Sans MS</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>log-font-size 8</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>show-on-task-bar 0</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>close-button-minimizes 1</I
-></SPAN
><br>
</P
>
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
-> #<SPAN
-CLASS="emphasis"
-><I
+> #<I
CLASS="EMPHASIS"
>hide-console</I
-></SPAN
><br>
</P
>
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="actions-file.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Configuration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="startup.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="config.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONFIGURATION">6. <SPAN
+NAME="CONFIGURATION"
+>6. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> Configuration</H1
+> Configuration</A
+></H1
><P
> All <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN530">6.1. Controlling <SPAN
+NAME="AEN555"
+>6.1. Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> with Your Web Browser</H2
+> with Your Web Browser</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><TD
><PRE
CLASS="SCREEN"
-> <H2
+> <H3
CLASS="BRIDGEHEAD"
-><A
-NAME="AEN539"> Privoxy Menu</H2
+> Privoxy Menu</H3
><P
></P
><TABLE
><H2
CLASS="SECT2"
><A
-NAME="CONFOVERVIEW">6.2. Configuration Files Overview</H2
+NAME="CONFOVERVIEW"
+>6.2. Configuration Files Overview</A
+></H2
><P
> For Unix, *BSD and Linux, all configuration files are located in
<TT
CLASS="QUOTE"
>"wake up"</SPAN
> requests
- must obviously be sent to the <SPAN
-CLASS="emphasis"
-><I
+ must obviously be sent to the <I
CLASS="EMPHASIS"
>old</I
-></SPAN
> listening address.</P
><P
> While under development, the configuration content is subject to change.
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="startup.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="config.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
Requests</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Templates"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="templates.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="CONTACT">11. Contacting the Developers, Bug Reporting and Feature
-Requests</H1
+NAME="CONTACT"
+>11. Contacting the Developers, Bug Reporting and Feature
+Requests</A
+></H1
><P
> We value your feedback. In fact, we rely on it to improve
<SPAN
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT">11.1. Get Support</H2
+NAME="CONTACT-SUPPORT"
+>11.1. Get Support</A
+></H2
><P
> For casual users, our support forum at
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-BUGS">11.2. Report Bugs</H2
+NAME="CONTACT-BUGS"
+>11.2. Report Bugs</A
+></H2
><P
-> Please report all bugs <SPAN
-CLASS="emphasis"
-><I
+> Please report all bugs <I
CLASS="EMPHASIS"
>only</I
-></SPAN
> through our
bug tracker:
<A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE">11.3. Request New Features</H2
+NAME="CONTACT-FEATURE"
+>11.3. Request New Features</A
+></H2
><P
> You are welcome to submit ideas on new features or other proposals
for improvement through our feature request tracker at
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-ADS">11.4. Report Ads or Other Actions-Related Problems</H2
+NAME="CONTACT-ADS"
+>11.4. Report Ads or Other Actions-Related Problems</A
+></H2
><P
> Please send feedback on ads that slipped through, innocent images that were blocked,
and any other problems relating to the <TT
TARGET="_top"
>ijbswa-announce</A
>
- list and available from our <A
+ list and available from our the <A
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>files section</A
+> of
+ our <A
HREF="http://sf.net/projects/ijbswa/"
TARGET="_top"
>project page</A
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-OTHER">11.5. Other</H2
+NAME="CONTACT-OTHER"
+>11.5. Other</A
+></H2
><P
>For any other issues, feel free to use the mailing lists. Technically interested users
and people who wish to contribute to the project are also welcome on the developers list!
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="templates.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="copyright.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Privoxy Copyright, License and History</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Contacting the Developers, Bug Reporting and Feature
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="seealso.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="COPYRIGHT">12. <SPAN
+NAME="COPYRIGHT"
+>12. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> Copyright, License and History</H1
+> Copyright, License and History</A
+></H1
><P
> Copyright © 2001, 2002 by Privoxy Developers <TT
CLASS="EMAIL"
><H2
CLASS="SECT2"
><A
-NAME="AEN3138">12.1. License</H2
+NAME="AEN3185"
+>12.1. License</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="HISTORY">12.2. History</H2
+NAME="HISTORY"
+>12.2. History</A
+></H2
><P
> In the beginning, there was the
<A
><H2
CLASS="SECT2"
><A
-NAME="AUTHORS">12.3. Authors</H2
+NAME="AUTHORS"
+>12.3. Authors</A
+></H2
><P
> Current Project Developers:</P
><P
><P
CLASS="LITERALLAYOUT"
> Rodrigo Barbosa (RPM specfiles)<br>
- Moritz Barsnick<br>
Hal Burgiss (docs)<br>
Alexander Lazic<br>
Gábor Lipták<br>
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="seealso.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>The Filter File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="actions-file.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="templates.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="FILTER-FILE">9. The Filter File</H1
+NAME="FILTER-FILE"
+>9. The Filter File</A
+></H1
><P
> All text substitutions that can be invoked through the
<TT
HREF="actions-file.html"
>actions files</A
>, the
- filter file is organized in sections, which are called <SPAN
-CLASS="emphasis"
-><I
+ filter file is organized in sections, which are called <I
CLASS="EMPHASIS"
>filters</I
-></SPAN
>
here. Each filter consists of a heading line, that starts with the
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>keyword</I
-></SPAN
> <TT
CLASS="LITERAL"
>FILTER:</TT
>, followed by
- the filter's <SPAN
-CLASS="emphasis"
-><I
+ the filter's <I
CLASS="EMPHASIS"
>name</I
-></SPAN
>, and a short (one line)
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>description</I
-></SPAN
> of what it does. Below that line
- come the <SPAN
-CLASS="emphasis"
-><I
+ come the <I
CLASS="EMPHASIS"
>jobs</I
-></SPAN
>, i.e. lines that define the actual
text substitutions. By convention, the name of a filter
- should describe what the filter <SPAN
-CLASS="emphasis"
-><I
+ should describe what the filter <I
CLASS="EMPHASIS"
>eliminates</I
-></SPAN
>. The
comment is used in the <A
HREF="http://config.privoxy.org/"
><H2
CLASS="SECT2"
><A
-NAME="AEN2944">9.1. Filter File Tutorial</H2
+NAME="AEN2983"
+>9.1. Filter File Tutorial</A
+></H2
><P
> Now, let's complete our <SPAN
CLASS="QUOTE"
></TABLE
></P
><P
-> But wait! Didn't the comment say that <SPAN
-CLASS="emphasis"
-><I
+> But wait! Didn't the comment say that <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> occurrences
of <SPAN
CLASS="QUOTE"
matches <SPAN
CLASS="QUOTE"
>"<script"</SPAN
->, followed by <SPAN
-CLASS="emphasis"
-><I
+>, followed by <I
CLASS="EMPHASIS"
>any</I
-></SPAN
> text, i.e.
it matches the whole page, from the start of the first <script> tag.</P
><P
CLASS="QUOTE"
>"document.referrer"</SPAN
>. The dot needed to
- be <SPAN
-CLASS="emphasis"
-><I
+ be <I
CLASS="EMPHASIS"
>escaped</I
-></SPAN
>, i.e. preceded by a backslash, to take away its
special meaning as a joker, and make it just a regular dot. So far, the meaning is:
Match from the start of the first <script> tag in a the page, up to, and including,
the text <SPAN
CLASS="QUOTE"
>"document.referrer"</SPAN
->, if <SPAN
-CLASS="emphasis"
-><I
+>, if <I
CLASS="EMPHASIS"
>both</I
-></SPAN
> are present
in the page (and appear in that order).</P
><P
text in between <SPAN
CLASS="QUOTE"
>"<script"</SPAN
-> and the <SPAN
-CLASS="emphasis"
-><I
+> and the <I
CLASS="EMPHASIS"
>first</I
-></SPAN
> occurrence
of <SPAN
CLASS="QUOTE"
CLASS="LITERAL"
>.*</TT
> will
- only span the text up to the <SPAN
-CLASS="emphasis"
-><I
+ only span the text up to the <I
CLASS="EMPHASIS"
>first</I
-></SPAN
> <SPAN
CLASS="QUOTE"
>"</script>"</SPAN
<TT
CLASS="LITERAL"
>"Not Your Business!"</TT
-> (<SPAN
-CLASS="emphasis"
-><I
+> (<I
CLASS="EMPHASIS"
>including</I
-></SPAN
>
the quotation marks!), followed by the text remembered as <TT
CLASS="LITERAL"
CLASS="SCREEN"
># The status bar is for displaying link targets, not pointless blahblah
#
-s/window\.status\s*=\s*['"].*?['"]/dUmMy=1/ig</PRE
+s/window\.status\s*=\s*(['"]).*?\1/dUmMy=1/ig</PRE
></TD
></TR
></TABLE
> construct means: <SPAN
CLASS="QUOTE"
>"a single
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>or</I
-></SPAN
> a double quote"</SPAN
->.</P
+>. Finally, <TT
+CLASS="LITERAL"
+>\1</TT
+> is
+ a backreference to the first parenthesis just like <TT
+CLASS="LITERAL"
+>$1</TT
+> above,
+ with the difference that in the <I
+CLASS="EMPHASIS"
+>pattern</I
+>, a backslash indicates
+ a backreference, whereas in the <I
+CLASS="EMPHASIS"
+>substitute</I
+>, it's the dollar.</P
><P
> So what does this job do? It replaces assignments of single- or double-quoted
strings to the <SPAN
CLASS="SCREEN"
># Kill OnUnload popups. Yummy. Test: http://www.zdnet.com/zdsubs/yahoo/tree/yfs.html
#
-s/(<body .*)onunload(.*>)/$1never$2/iU</PRE
+s/(<body [^>]*)onunload(.*>)/$1never$2/iU</PRE
></TD
></TR
></TABLE
TARGET="_top"
>OnUnload
event binding</A
-> in the HTML DOM was a <SPAN
-CLASS="emphasis"
-><I
+> in the HTML DOM was a <I
CLASS="EMPHASIS"
>CRIME</I
-></SPAN
>.
When I close a browser window, I want it to close and die. Basta.
This job replaces the <SPAN
CLASS="LITERAL"
>i</TT
> option makes the pattern matching
- case-insensitive.</P
+ case-insensitive. Also note that ungreedy matching alone doesn't always guarantee
+ a minimal match: In the first parenthesis, we had to use <TT
+CLASS="LITERAL"
+>[^>]*</TT
+>
+ instead of <TT
+CLASS="LITERAL"
+>.*</TT
+> to prevent the match from exceeding the
+ <body> tag if it doesn't contain <SPAN
+CLASS="QUOTE"
+>"OnUnload"</SPAN
+>, but the page's
+ content does.</P
><P
> The last example is from the fun department:</P
><P
#
s* industry[ -]leading \
| cutting[ -]edge \
+| customer[ -]focused \
+| market[ -]driven \
| award[ -]winning # Comments are OK, too! \
| high[ -]performance \
| solutions[ -]based \
CLASS="LITERAL"
>x</TT
> option in this job turns on extended syntax, and allows for
- e.g. the liberal use of (non-interpreted!) whitespace for nicer formatting.</P
+ e.g. the liberal use of (non-interpreted!) whitespace for nicer formatting. </P
><P
> You get the idea?</P
></DIV
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="actions-file.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="templates.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
<HTML
><HEAD
><TITLE
->Privoxy User Manual</TITLE
+>Privoxy 2.9.16 User Manual</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="NEXT"
TITLE="Introduction"
HREF="introduction.html"><LINK
><H1
CLASS="TITLE"
><A
-NAME="AEN2">Privoxy User Manual</H1
+NAME="AEN2"
+>Privoxy 2.9.16 User Manual</A
+></H1
><P
CLASS="PUBDATE"
> <SUB
>Copyright</A
> © 2001, 2002 by
<A
-HREF="http://www.privoxy.org"
+HREF="http://www.privoxy.org/"
TARGET="_top"
>Privoxy Developers</A
>
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 1.123.2.7 2002/06/09 00:29:34 hal9 Exp $<BR></P
+>$Id: user-manual.sgml,v 1.123.2.11 2002/07/26 15:20:31 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN9"><P
+NAME="AEN9"
+></A
+><P
></P
><P
> The <I
><DT
>2.1.6. <A
HREF="installation.html#INSTALLATION-MAC"
->Max OSX</A
+>Mac OSX</A
></DT
><DT
>2.1.7. <A
HREF="installation.html#INSTALLATION-SOURCE"
>Building from Source</A
></DT
+><DT
+>2.3. <A
+HREF="installation.html#INSTALLATION-KEEPUPDATED"
+>Keeping your Installation Up-to-Date</A
+></DT
></DL
></DD
><DT
><DT
>5.7. <A
HREF="startup.html#START-MACOSX"
->MAX OSX</A
+>Mac OSX</A
></DT
><DT
>5.8. <A
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN530"
+HREF="configuration.html#AEN555"
>Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN1584"
+HREF="actions-file.html#AEN1610"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN1591"
+HREF="actions-file.html#AEN1617"
>How to Edit</A
></DT
><DT
><DD
><DL
><DT
+>22<A
+HREF="actions-file.html#AEN1648"
+></A
+></DT
+><DT
>8.4.1. <A
-HREF="actions-file.html#AEN1655"
+HREF="actions-file.html#AEN1681"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN1717"
+HREF="actions-file.html#AEN1743"
>The Path Pattern</A
></DT
></DL
></DT
><DT
>8.5.21. <A
-HREF="actions-file.html#AEN2635"
+HREF="actions-file.html#AEN2671"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN2687"
+HREF="actions-file.html#AEN2723"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN2841"
+HREF="actions-file.html#AEN2880"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN2944"
+HREF="filter-file.html#AEN2983"
>Filter File Tutorial</A
></DT
></DL
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN3138"
+HREF="copyright.html#AEN3185"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN3388"
+HREF="appendix.html#AEN3435"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="introduction.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Installation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="introduction.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="upgradersnote.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION">2. Installation</H1
+NAME="INSTALLATION"
+>2. Installation</A
+></H1
><P
> <SPAN
CLASS="APPLICATION"
> installation on your system, you
will need to remove it. On some platforms, this may be done for you as part
of their installation procedure. (See below for your platform). In any case
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>be sure to backup your old configuration if it is valuable to
you.</I
-></SPAN
> See the <A
HREF="upgradersnote.html"
>note to
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-PACKAGES">2.1. Binary Packages</H2
+NAME="INSTALLATION-PACKAGES"
+>2.1. Binary Packages</A
+></H2
><P
>How to install the binary packages depends on your operating system:</P
><DIV
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-RPM">2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
+NAME="INSTALLATION-PACK-RPM"
+>2.1.1. Red Hat, SuSE and Conectiva RPMs</A
+></H3
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-2.9.15-1.rpm</TT
+>rpm -Uvh privoxy-2.9.16-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
CLASS="APPLICATION"
>Privoxy</SPAN
> will
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>not</I
-></SPAN
> be automatically started on system boot. You will
need to enable that using <B
CLASS="COMMAND"
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-2.9.15-1.src.rpm</TT
+>rpm --rebuild privoxy-2.9.16-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-DEB">2.1.2. Debian</H3
+NAME="INSTALLATION-DEB"
+>2.1.2. Debian</A
+></H3
><P
> DEBs can be installed with <TT
CLASS="LITERAL"
>dpkg -i
- privoxy_2.9.15-1.deb</TT
+ privoxy_2.9.16-1.deb</TT
>, and will use
<TT
CLASS="FILENAME"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-WIN">2.1.3. Windows</H3
+NAME="INSTALLATION-PACK-WIN"
+>2.1.3. Windows</A
+></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">2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
+NAME="INSTALLATION-PACK-BINTGZ"
+>2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
+></H3
><P
> Create a new directory, <TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-OS2">2.1.5. OS/2</H3
+NAME="INSTALLATION-OS2"
+>2.1.5. OS/2</A
+></H3
><P
> First, make sure that no previous installations of
<SPAN
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-MAC">2.1.6. Max OSX</H3
+NAME="INSTALLATION-MAC"
+>2.1.6. Mac OSX</A
+></H3
><P
> Unzip the downloaded package (you can either double-click on the file
- in the finder, or on the desktop if you downloaded it there). Then,
- double-click on the package installer icon and follow the installation
- process.
+ in the finder, or on the desktop if you downloaded it there). The
+ Privoxy.pkg package should appear after unzipping. Then,
+ double-click on that Privoxy.pkg package installer icon and follow
+ the installation process.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> will be installed in the subdirectory
+> will be installed in the folder
<TT
CLASS="LITERAL"
->/Applications/Privoxy.app</TT
+>/Library/Privoxy</TT
>.
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> will set itself up to start
- automatically on system bring-up via
+ It will run automatically whenever you start up. To prevent it from
+ running automatically, remove or rename the folder
<TT
CLASS="LITERAL"
->/System/Library/StartupItems/Privoxy</TT
->.</P
+>/Library/StartupItems/Privoxy</TT
+>. </P
+><P
+> To run Privoxy by hand, double-click on
+ <TT
+CLASS="LITERAL"
+>RunPrivoxy.command</TT
+>.
+ To run Privoxy from Terminal, execute
+ <TT
+CLASS="LITERAL"
+>/Library/Privoxy/RunPrivoxy.command</TT
+>. </P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-AMIGA">2.1.7. AmigaOS</H3
+NAME="INSTALLATION-AMIGA"
+>2.1.7. AmigaOS</A
+></H3
><P
> Copy and then unpack the <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-SOURCE">2.2. Building from Source</H2
+NAME="INSTALLATION-SOURCE"
+>2.2. Building from Source</A
+></H2
><P
> The most convenient way to obtain the <SPAN
CLASS="APPLICATION"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.15-beta</PRE
+> tar xzvf privoxy-2.9.16-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.16-beta</PRE
></TD
></TR
></TABLE
>developer manual</A
>.</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="INSTALLATION-KEEPUPDATED"
+>2.3. Keeping your Installation Up-to-Date</A
+></H2
+><P
+> As user feedback comes in and development continues, we will make updated versions
+ of both the software and the main <A
+HREF="actions-file.html"
+>actions file</A
+>
+ (<TT
+CLASS="LITERAL"
+>default.action</TT
+>) available for download.</P
+><P
+> If you wish to receive an email notification whenever we release updates of
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> or the actions file, <A
+HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
+TARGET="_top"
+>subscribe
+ to our announce mailing list</A
+>, ijbswa-announce@lists.sourceforge.net.</P
+><P
+> Both can be downloaded from the <A
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>files
+ section</A
+> on <A
+HREF="http://sourceforge.net/"
+TARGET="_top"
+>SourceForge</A
+>.</P
+><P
+> In order not to loose your personal changes and adjustments when updating
+ to the latest <TT
+CLASS="LITERAL"
+>default.action</TT
+> file we <I
+CLASS="EMPHASIS"
+>strongly
+ recommend</I
+> that you use <TT
+CLASS="LITERAL"
+>user.action</TT
+> for your
+ customization of <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>. See the <A
+HREF="actions-file.html"
+>Chapter on actions files</A
+> for details.</P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="introduction.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="upgradersnote.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Introduction</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Installation"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="INTRODUCTION">1. Introduction</H1
+NAME="INTRODUCTION"
+>1. Introduction</A
+></H1
><P
> This documentation is included with the current beta version of
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.2.9.15,
+>, v.2.9.16,
and is mostly complete at this point. The most up to date reference for the
time being is still the comments in the source files and in the individual
configuration files. Development of version 3.0 is currently nearing
><P
> Since this is a beta version, not all new features are well tested. This
documentation may be slightly out of sync as a result (especially with
- CVS sources). And there <SPAN
-CLASS="emphasis"
-><I
+ CVS sources). And there <I
CLASS="EMPHASIS"
>may be</I
-></SPAN
> bugs, though hopefully
not many! </P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="FEATURES">1.1. Features</H2
+NAME="FEATURES"
+>1.1. Features</A
+></H2
><P
> In addition to <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Privoxy User Manual</TD
+>Privoxy 2.9.16 User Manual</TD
><TD
WIDTH="34%"
ALIGN="center"
>Quickstart to Using Privoxy</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Note to Upgraders"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="upgradersnote.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="startup.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="QUICKSTART">4. Quickstart to Using <SPAN
+NAME="QUICKSTART"
+>4. Quickstart to Using <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
+></A
></H1
><P
> <P
><H2
CLASS="SECT2"
><A
-NAME="QUICKSTART-AD-BLOCKING">4.1. Quickstart to Ad Blocking</H2
+NAME="QUICKSTART-AD-BLOCKING"
+>4.1. Quickstart to Ad Blocking</A
+></H2
><P
> Ad blocking is but one of <SPAN
CLASS="APPLICATION"
>"problem"</SPAN
> sites, and to spend more time adjusting the
configuration to solve these unintended consequences. In short, there is
- not an easy way to eliminate <SPAN
-CLASS="emphasis"
-><I
+ not an easy way to eliminate <I
CLASS="EMPHASIS"
>all</I
-></SPAN
> ads. Either take
- the easy way and settle for <SPAN
-CLASS="emphasis"
-><I
+ the easy way and settle for <I
CLASS="EMPHASIS"
>most</I
-></SPAN
> ads blocked with the
default configuration, or jump in and tweak it for your personal surfing
habits and preferences.</P
>block</A
></TT
> action somewhere in the
- configuration, <SPAN
-CLASS="emphasis"
-><I
+ configuration, <I
CLASS="EMPHASIS"
>and</I
-></SPAN
>, it must also match an
<TT
CLASS="LITERAL"
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>pattern</I
-></SPAN
> - a checkerboard pattern, so that an ad
replacement is obvious. This is the default.
</TD
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>blank</I
-></SPAN
> - A very small empty GIF image is displayed.
This is the so-called <SPAN
CLASS="QUOTE"
><TBODY
><TR
><TD
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>http://<URL></I
-></SPAN
> - A redirect to any image anywhere
of the user's choosing (advanced usage).
</TD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN355"><P
+NAME="AEN374"
+></A
+><P
><B
>Figure 1. Actions Files in Use</B
></P
CLASS="MEDIAOBJECT"
><P
><IMG
-SRC="../images/files-in-use.jpg"></P
+SRC="../images/files-in-use.jpg"
+ALT="[ Screenshot of Actions Files in Use ]"
+></IMG
+></P
></DIV
></DIV
>
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="upgradersnote.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="startup.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>See Also</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Copyright, License and History"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="copyright.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="appendix.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="SEEALSO">13. See Also</H1
+NAME="SEEALSO"
+>13. See Also</A
+></H1
><P
> Other references and sites of interest to <SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="copyright.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="appendix.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Starting Privoxy</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="quickstart.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="STARTUP">5. Starting <SPAN
+NAME="STARTUP"
+>5. Starting <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
+></A
></H1
><P
> Before launching <SPAN
127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
used port 8000). This is the one configuration step that must be done!</P
><P
+> Please note that <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> can only proxy HTTP and
+ HTTPS traffic. It will not work with FTP or other protocols.</P
+><P
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN404"><P
+NAME="AEN425"
+></A
+><P
><B
>Figure 2. Proxy Configuration (Mozilla)</B
></P
CLASS="MEDIAOBJECT"
><P
><IMG
-SRC="../images/proxy_setup.jpg"></P
+SRC="../images/proxy_setup.jpg"
+ALT="[ Screenshot of Mozilla Proxy Configuration ]"
+></IMG
+></P
></DIV
></DIV
>
><H2
CLASS="SECT2"
><A
-NAME="START-REDHAT">5.1. Red Hat and Conectiva</H2
+NAME="START-REDHAT"
+>5.1. Red Hat and Conectiva</A
+></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">5.2. Debian</H2
+NAME="START-DEBIAN"
+>5.2. Debian</A
+></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">5.3. SuSE</H2
+NAME="START-SUSE"
+>5.3. SuSE</A
+></H2
><P
>We use a script. It will use the file <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="START-WINDOWS">5.4. Windows</H2
+NAME="START-WINDOWS"
+>5.4. Windows</A
+></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">5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</H2
+NAME="START-UNICES"
+>5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</A
+></H2
><P
>Example Unix startup command:</P
><P
><H2
CLASS="SECT2"
><A
-NAME="START-OS2">5.6. OS/2</H2
+NAME="START-OS2"
+>5.6. OS/2</A
+></H2
><P
> During installation, <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="START-MACOSX">5.7. MAX OSX</H2
+NAME="START-MACOSX"
+>5.7. Mac OSX</A
+></H2
><P
> During installation, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> is configured to
- start automatically when the system restarts. You can start it manually
- through the Terminal with these commands:</P
+ start automatically when the system restarts. To run Privoxy by hand,
+ double-click on the <TT
+CLASS="LITERAL"
+>RunPrivoxy.command</TT
+> icon in the
+ <TT
+CLASS="LITERAL"
+>/Library/Privoxy</TT
+> folder. Or, type this command
+ in the Terminal:</P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> cd /Applications/Privoxy.app
- ./privoxy</PRE
+> /Library/Privoxy/RunPrivoxy.command
+ </PRE
></TD
></TR
></TABLE
></P
+><P
+> If you are not logged in as an administrator, you will be asked for the
+ administrator password when starting <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ by hand.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="START-AMIGAOS">5.8. AmigaOS</H2
+NAME="START-AMIGAOS"
+>5.8. AmigaOS</A
+></H2
><P
> Start <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="CMDOPTIONS">5.9. Command Line Options</H2
+NAME="CMDOPTIONS"
+>5.9. Command Line Options</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><UL
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>--version</I
-></SPAN
>
</P
><P
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>--help</I
-></SPAN
>
</P
><P
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>--no-daemon</I
-></SPAN
>
</P
><P
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>--pidfile FILE</I
-></SPAN
>
</P
><P
-> On startup, write the process ID to <SPAN
-CLASS="emphasis"
-><I
+> On startup, write the process ID to <I
CLASS="EMPHASIS"
>FILE</I
-></SPAN
>. Delete the
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>FILE</I
-></SPAN
> on exit. Failure to create or delete the
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>FILE</I
-></SPAN
-> is non-fatal. If no <SPAN
-CLASS="emphasis"
-><I
+> is non-fatal. If no <I
CLASS="EMPHASIS"
>FILE</I
-></SPAN
>
option is given, no PID file will be used. Unix only.
</P
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>--user USER[.GROUP]</I
-></SPAN
>
</P
><P
> After (optionally) writing the PID file, assume the user ID of
- <SPAN
-CLASS="emphasis"
-><I
+ <I
CLASS="EMPHASIS"
>USER</I
-></SPAN
>, and if included the GID of GROUP. Exit if the
privileges are not sufficient to do so. Unix only.
</P
></LI
><LI
><P
-> <SPAN
-CLASS="emphasis"
-><I
+> <I
CLASS="EMPHASIS"
>configfile</I
-></SPAN
>
</P
><P
-> If no <SPAN
-CLASS="emphasis"
-><I
+> If no <I
CLASS="EMPHASIS"
>configfile</I
-></SPAN
> is included on the command line,
<SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="quickstart.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="configuration.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Templates</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Filter File"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="filter-file.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="TEMPLATES">10. Templates</H1
+NAME="TEMPLATES"
+>10. Templates</A
+></H1
><P
> All <SPAN
CLASS="APPLICATION"
TARGET="_top"
>web-based
user interface</A
->, are generated from <SPAN
-CLASS="emphasis"
-><I
+>, are generated from <I
CLASS="EMPHASIS"
>templates</I
-></SPAN
>.
(<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> fills at run time. You can
edit the templates with a normal text editor, should you want to customize them.
- (<SPAN
-CLASS="emphasis"
-><I
+ (<I
CLASS="EMPHASIS"
>Not recommended for the casual user</I
-></SPAN
>). Note that
just like in configuration files, lines starting with <TT
CLASS="LITERAL"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="filter-file.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="contact.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
>Note to Upgraders</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 2.9.16 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><DIV
CLASS="NAVHEADER"
><TABLE
-SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 2.9.16 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="quickstart.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
><H1
CLASS="SECT1"
><A
-NAME="UPGRADERSNOTE">3. Note to Upgraders</H1
+NAME="UPGRADERSNOTE"
+>3. Note to Upgraders</A
+></H1
><P
> There are very significant changes from earlier
<SPAN
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="installation.html"
-ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
-ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="quickstart.html"
-ACCESSKEY="N"
>Next</A
></TD
></TR
projects / privoxy.git / commitdiff