><H3
CLASS="SECT2"
><A
-NAME="AEN335"
+NAME="AEN341"
>3.1. What exactly is an <SPAN
CLASS="QUOTE"
>"actions"</SPAN
><H3
CLASS="SECT2"
><A
-NAME="AEN358"
+NAME="AEN364"
>3.3. How are actions files configured? What is the easiest
way to do this?</A
></H3
><H3
CLASS="SECT2"
><A
-NAME="AEN367"
+NAME="AEN373"
>3.4. There are several different <SPAN
CLASS="QUOTE"
>"actions"</SPAN
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="AEN465"
+NAME="AEN470"
>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 now 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="AEN512"
+NAME="AEN521"
>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="AEN529"
+NAME="AEN538"
>3.14. Why would anybody want to see a checkerboard pattern?</A
></H3
><P
><H3
CLASS="SECT2"
><A
-NAME="AEN535"
+NAME="AEN544"
>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
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
> 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