HREF="misc.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css"></HEAD
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#EEEEEE"
><H3
CLASS="SECT2"
><A
-NAME="AEN342"
+NAME="AEN360"
>3.1. What exactly is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN365"
+NAME="AEN383"
>3.3. How are actions files configured? What is the easiest
way to do this?</A
></H3
><H3
CLASS="SECT2"
><A
-NAME="AEN374"
+NAME="AEN392"
>3.4. There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
the differences?</A
></H3
><P
-> Three actions files
- are being included by the developers, to be used for
- different purposes: These are
- <TT
-CLASS="FILENAME"
->default.action</TT
->, the <SPAN
-CLASS="QUOTE"
->"main"</SPAN
-> actions file
- which is actively maintained by the <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- developers and typically sets the default policies, <TT
-CLASS="FILENAME"
->user.action</TT
->, where users are encouraged
- to make their private customizations, and <TT
-CLASS="FILENAME"
->standard.action</TT
->,
- which is for internal <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> use only.
- Please see <A
+> Please have a look at the <A
HREF="../user-manual/actions-file.html"
TARGET="_top"
>the actions chapter</A
HREF="../user-manual/index.html"
TARGET="_top"
>User Manual</A
-> for a more
- detailed explanation.</P
-><P
-> Earlier versions included three different versions of the
- <TT
-CLASS="FILENAME"
->default.action</TT
-> file. The new scheme allows for
- greater flexibility of local configuration, and for browser based
- selection of pre-defined <SPAN
-CLASS="QUOTE"
->"aggressiveness"</SPAN
-> levels.</P
+> for a detailed explanation.</P
></DIV
><DIV
CLASS="SECT2"
>3.5. Where can I get updated Actions Files?</A
></H3
><P
-> Based on your feedback and the continuing development, updates of
- <TT
+> Based on your feedback and the continuing development, updates of
+ <TT
CLASS="FILENAME"
>default.action</TT
> will be
-
made available from time to time on the <A
+
made available from time to time on the <A
HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
TARGET="_top"
>files section</A
HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
TARGET="_top"
>subscribe
- to our announce mailing list</A
+ to our announce mailing list</A
>, ijbswa-announce@lists.sourceforge.net.
</P
></DIV
CLASS="QUOTE"
>"improved"</SPAN
> versions and it is
- therefore strongly recommended to use the newer configuration files.
+ therefore strongly recommended to install the newer configuration files
+ and merge back your modifications.
</P
></DIV
><DIV
CLASS="APPLICATION"
>Privoxy</SPAN
> for multiple untrusted users (e.g. in
- a LAN), you will probably want to make sure that the the web-based
- editor and remote toggle features are <SPAN
+ a LAN) or aren't entirely in control of your own browser, you will probably want
+ to make sure that the the web-based editor and remote toggle features are
+ <SPAN
CLASS="QUOTE"
>"off"</SPAN
> by setting <SPAN
>.
</P
><P
-> Note that in the default configuration, only local users (i.e. those on
- <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->) can connect to <SPAN
+> As of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->,
- so this is (normally) not a security problem.
+> 3.0.7 these options are disabled by default.
</P
></DIV
><DIV
><H3
CLASS="SECT2"
><A
-NAME="AEN472"
+NAME="AEN480"
>3.11. What is the <TT
CLASS="FILENAME"
>default.filter</TT
CLASS="EMPHASIS"
>filters</I
></SPAN
-> as supplied by the developers are defined.
+> as supplied by the developers are defined.
Filters are a special subset of actions that can be used to modify or
- remove, web page content on the fly. Filters apply to <SPAN
+ remove web page content or headers on the fly. Content filters can
+ be applied to <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>anything</I
></SPAN
->
- in the page source (and optionally both client and server headers), including
- HTML tags, and JavaScript. Regular expressions are used to accomplish this.
- There are a number of pre-defined filters to deal with common annoyances. The
+> in the page source,
+ header filters can be applied to either server or client headers.
+ Regular expressions are used to accomplish this.</P
+><P
+> There are a number of pre-defined filters to deal with common annoyances. The
filters are only defined here, to invoke them, you need to use the
<A
HREF="../user-manual/actions-file.html#FILTER"
>filter</TT
>
action</A
-> in one of the actions files. Filtering is automatically
- disabled for inappropriate MIME types. Filters should
+> in one of the actions files. Content filtering is automatically
+ disabled for inappropriate MIME types, but if you know better than Privoxy
+ what should or should not be filtered you can filter any content you like.</P
+><P
+> Filters should
<SPAN
CLASS="emphasis"
><I
HREF="http://config.privoxy.org/show-status"
TARGET="_top"
>web-based actions file editor</A
->
- Note
- that the custom actions editor must be explicitly enabled in the main config file
- (see <A
+>.
+ Note that the custom actions editor must be explicitly enabled in
+ the main config file (see <A
HREF="../user-manual/config.html#ENABLE-EDIT-ACTIONS"
TARGET="_top"
>enable-edit-actions</A
->). </P
+>).</P
+><P
+> If you intend to develop your own filters, you might want to have a look at
+ <A
+HREF="http://www.fabiankeil.de/sourcecode/pft/"
+TARGET="_top"
+>Privoxy-Filter-Test</A
+>.</P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN519"
+NAME="AEN531"
>3.13. Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</A
></H3
><P
><H3
CLASS="SECT2"
><A
-NAME="AEN536"
+NAME="AEN548"
>3.14. Why would anybody want to see a checkerboard pattern?</A
></H3
><P
><H3
CLASS="SECT2"
><A
-NAME="AEN542"
+NAME="AEN554"
>3.15. I see some images being replaced with text
instead of the checkerboard image. Why and how do I get rid of this?</A
></H3
>srvany.exe</B
>.
See the discussion at <A
-HREF="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118"
+HREF="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118"
TARGET="_top"
>http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</A
>,
CLASS="LITERAL"
>Host</TT
> header is required by HTTP/1.1 and as most
- web sites don't work if it isn't set, this limitation shouldn't be a
- problem.</P
+ web sites rely on it anyway, this limitation shouldn't be a problem.</P
><P
> Please refer to your packet filter's documentation to learn how to
intercept and redirect traffic into <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->. Afterward you just have
- to configure <SPAN
+>.
+ Afterward you just have to configure <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> to
<A
HREF="../user-manual/config.html#ACCEPT-INTERCEPTED-REQUESTS"
TARGET="_top"
->accept intercepted requests</A
+>accept
+ intercepted requests</A
>.</P
></DIV
><DIV
CLASS="SECT2"
><A
NAME="OUTLOOK"
->3.21. How can I configure Privoxy for use with Outlook
- Express?</A
+>3.21. How can I configure Privoxy for use with Outlook?</A
></H3
><P
-> <SPAN
+> Versions of <SPAN
CLASS="APPLICATION"
->Outlook Express</SPAN
-> uses <SPAN
+>Outlook</SPAN
+> prior to Office 2007, use
+ <SPAN
CLASS="APPLICATION"
>Internet Explorer</SPAN
->
- components to both render HTML, and fetch any HTTP requests that may be embedded in an HTML email.
- So however you have <SPAN
+> components to both render HTML,
+ and fetch any HTTP requests that may be embedded in an HTML email. So however
+ you have <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> configured to work
- with IE, this configuration should automatically be shared.</P
+> configured to work with IE, this
+ configuration should automatically be shared, at least with older version of
+ Internet Explorer.</P
+><P
+> Starting with Office 2007, Microsoft is instead using the MS-Word rendering
+ engine with Outlook. It is unknown whether this can be configured to use a
+ proxy.
+ </P
></DIV
><DIV
CLASS="SECT2"
> For a good discussion of some of the issues involved (including privacy and
security issues), see
<A
-HREF="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118"
+HREF="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118"
TARGET="_top"
>http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</A
>.</P
method that browsers can use to store data between pages, or between browser
sessions. Sometimes there is a good reason for this, and the user's life is a
bit easier as a result. But there is a long history of some websites taking
- advantage of this layer of trust, and using the data they glean from you and
+ advantage of this layer of trust, and using the data they glean from you and
your browsing habits for their own purposes, and maybe to your potential
detriment. Such sites are using you and storing their data on your system.
That is why the privacy conscious watch from whom those cookies come, and why
> This allows access to only those three sites by first blocking all URLs, and
then subsequently allowing three specific exceptions.</P
><P
-> A more interesting approach is <SPAN
+> Another approach is <SPAN
CLASS="APPLICATION"
>Privoxy's</SPAN
>
>. See the <A
HREF="../user-manual/config.html#TRUSTFILE"
TARGET="_top"
->User Manual Trust</A
+>Trust documentation</A
>
- documentation.</P
+ for details.</P
><P
> These are fairly simple approaches and are not completely foolproof. There
are various other configuration options that should be disabled (described
>the User Manual</A
>)
so that users can't modify their own configuration and easily circumvent the
- whitelist. </P
+ whitelist.</P
></DIV
><DIV
CLASS="SECT2"
CLASS="FILENAME"
>templates</TT
>. Knowing something about HTML syntax
- will of course be helpful. Be forewarned that the default templates are
- subject to being overwritten during upgrades. You can, however, create
- completely new templates by specifying an alternate path for them in the main
+ will of course be helpful.</P
+><P
+> Be forewarned that the default templates are subject to being overwritten
+ during upgrades. You can, however, create completely new templates,
+ place them in another directory and specify the alternate path in the main
<TT
CLASS="FILENAME"
>config</TT
+>
. For details, have a look at the <A
HREF="../user-manual/config.html#templdir"
TARGET="_top"
>templdir</A
> page?</A
></H3
><P
-> There is more than one way to do it.</P
+> There is more than one way to do it (although Perl is not involved).</P
><P
> Editing the BLOCKED template page (see above) may dissuade some users, but
this method is easily circumvented. Where you need this level of control, you
- should build <SPAN
+ might want to build <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> from source, and enable various features that are
+> from source, and disable various features that are
available as compile-time options. You should
<B
CLASS="COMMAND"
> does not allow easy bypassing of blocked sites, or changing the
current configuration via any connected user's web browser.</P
><P
-> Note that all of these features can also be toggled on/off via options in
+> Finally, all of these features can also be toggled on/off via options in
<SPAN
CLASS="APPLICATION"
>Privoxy's</SPAN
projects / privoxy.git / blobdiff