>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
projects / privoxy.git / blobdiff