CLASS="SECT1"
><A
NAME="APPENDIX"
->11. Appendix</A
+>15. Appendix</A
></H1
><DIV
CLASS="SECT2"
CLASS="SECT2"
><A
NAME="REGEX"
->11.1. Regular Expressions</A
+>15.1. Regular Expressions</A
></H2
><P
> <SPAN
><H2
CLASS="SECT2"
><A
-NAME="AEN2545"
->11.2. <SPAN
+NAME="AEN2625"
+>15.2. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>'s Internal Pages</A
Privoxy main page:
</P
><A
-NAME="AEN2560"
+NAME="AEN2640"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN2567"
+NAME="AEN2647"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN2572"
+NAME="AEN2652"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN2577"
+NAME="AEN2657"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN2582"
+NAME="AEN2662"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN2588"
+NAME="AEN2668"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN2592"
+NAME="AEN2672"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN2595"
+NAME="AEN2675"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="SECT3"
><A
NAME="BOOKMARKLETS"
->11.2.1. Bookmarklets</A
+>15.2.1. Bookmarklets</A
></H3
><P
> Below are some <SPAN
CLASS="SECT2"
><A
NAME="CHAIN"
->11.3. Chain of Events</A
+>15.3. Chain of Events</A
></H2
><P
> Let's take a quick look at the basic sequence of events when a web page is
>Privoxy</SPAN
> checks to see if the URL
matches any <A
-HREF="configuration.html#BLOCK"
+HREF="actions-file.html#BLOCK"
TARGET="_top"
><SPAN
CLASS="QUOTE"
> patterns. If
so, the URL is then blocked, and the remote web server will not be contacted.
<A
-HREF="configuration.html#HANDLE-AS-IMAGE"
+HREF="actions-file.html#HANDLE-AS-IMAGE"
TARGET="_top"
><SPAN
CLASS="QUOTE"
>"BLOCKED"</SPAN
> page is sent back. Otherwise, if it does match,
an image is returned. The type of image depends on the setting of <A
-HREF="configuration.html#SET-IMAGE-BLOCKER"
+HREF="actions-file.html#SET-IMAGE-BLOCKER"
TARGET="_top"
><SPAN
CLASS="QUOTE"
><LI
><P
> If the URL pattern matches the <A
-HREF="configuration.html#FAST-REDIRECTS"
+HREF="actions-file.html#FAST-REDIRECTS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
><P
> Now the rest of the client browser's request headers are processed. If any
of these match any of the relevant actions (e.g. <A
-HREF="configuration.html#HIDE-USER-AGENT"
+HREF="actions-file.html#HIDE-USER-AGENT"
TARGET="_top"
><SPAN
CLASS="QUOTE"
things, the MIME type (document type) and encoding. The headers are then
filtered as deterimed by the
<A
-HREF="configuration.html#PREVENT-SETTING-COOKIES"
+HREF="actions-file.html#PREVENT-SETTING-COOKIES"
TARGET="_top"
><SPAN
CLASS="QUOTE"
></A
>,
<A
-HREF="configuration.html#SESSION-COOKIES-ONLY"
+HREF="actions-file.html#SESSION-COOKIES-ONLY"
TARGET="_top"
><SPAN
CLASS="QUOTE"
></A
>,
and <A
-HREF="configuration.html#DOWNGRADE-HTTP-VERSION"
+HREF="actions-file.html#DOWNGRADE-HTTP-VERSION"
TARGET="_top"
><SPAN
CLASS="QUOTE"
><LI
><P
> If the <A
-HREF="configuration.html#KILL-POPUPS"
+HREF="actions-file.html#KILL-POPUPS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
><LI
><P
> If a <A
-HREF="configuration.html#FILTER"
+HREF="actions-file.html#FILTER"
TARGET="_top"
><SPAN
CLASS="QUOTE"
></A
>
or <A
-HREF="configuration.html#DEANIMATE-GIFS"
+HREF="actions-file.html#DEANIMATE-GIFS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
</P
><P
> If neither <A
-HREF="configuration.html#FILTER"
+HREF="actions-file.html#FILTER"
TARGET="_top"
><SPAN
CLASS="QUOTE"
></A
>
or <A
-HREF="configuration.html#DEANIMATE-GIFS"
+HREF="actions-file.html#DEANIMATE-GIFS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
CLASS="SECT2"
><A
NAME="ACTIONSANAT"
->11.4. Anatomy of an Action</A
+>15.4. Anatomy of an Action</A
></H2
><P
> The way <SPAN
>Privoxy</SPAN
> applies
<A
-HREF="configuration.html#ACTIONS"
+HREF="actions-file.html#ACTIONS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
></A
>
and <A
-HREF="configuration.html#FILTER"
+HREF="actions-file.html#FILTER"
TARGET="_top"
><SPAN
CLASS="QUOTE"
> will tell us
how the current configuration will handle it. This will not
help with filtering effects (i.e. the <A
-HREF="configuration.html#FILTER"
+HREF="actions-file.html#FILTER"
TARGET="_top"
><SPAN
CLASS="QUOTE"
><P
> This tells us how we have defined our
<A
-HREF="configuration.html#ACTIONS"
+HREF="actions-file.html#ACTIONS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
>".google.com"</SPAN
>. The first is negating our previous cookie setting,
which was for <A
-HREF="configuration.html#SESSION-COOKIES-ONLY"
+HREF="actions-file.html#SESSION-COOKIES-ONLY"
TARGET="_top"
><SPAN
CLASS="QUOTE"
>off</I
> any
<A
-HREF="configuration.html#FAST-REDIRECTS"
+HREF="actions-file.html#FAST-REDIRECTS"
TARGET="_top"
><SPAN
CLASS="QUOTE"
CLASS="QUOTE"
>"+imageblock"</SPAN
>. (<A
-HREF="configuration.html#ALIASES"
+HREF="actions-file.html#ALIASES"
TARGET="_top"
><SPAN
CLASS="QUOTE"
>"ad.doubleclick.net"</SPAN
>
is done here -- as both a <A
-HREF="configuration.html#BLOCK"
+HREF="actions-file.html#BLOCK"
TARGET="_top"
><SPAN
CLASS="QUOTE"
>and</I
> an
<A
-HREF="configuration.html#HANDLE-AS-IMAGE"
+HREF="actions-file.html#HANDLE-AS-IMAGE"
TARGET="_top"
><SPAN
CLASS="QUOTE"