a blank line right after a <para>, <literallayout>, <screen>
or just before the closing tag causes docbook 3.1 to generate
a ' '
eg: this sgml
following patterns</quote>, and <literal>-block</literal> means <quote>don't
block URLs that match the following patterns, even if <literal>+block</literal>
previously applied.</quote>
</para>
<para>
Again, actions are invoked by placing them on a line, enclosed in curly braces and
leads to this html:
>, and <TT
CLASS="LITERAL"
>-block</TT
> means <SPAN
CLASS="QUOTE"
>"don't
block URLs that match the following patterns, even if <TT
CLASS="LITERAL"
>+block</TT
>
previously applied."</SPAN
> </P
><P
> Again, actions are invoked by placing them on a line, enclosed in curly braces and
having " " right after the "</SPAN>" is just wrong.
details</ulink>. You should also flush your browser's memory and disk
cache to get rid of any cached junk items, and remove any stored
<ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
details</ulink>. You should also flush your browser's memory and disk
cache to get rid of any cached junk items, and remove any stored
<ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
system. Check that no <application>Junkbuster</application>
or <application>Privoxy</application> objects are in
your startup folder.
system. Check that no <application>Junkbuster</application>
or <application>Privoxy</application> objects are in
your startup folder.
<literallayout>
<guibutton>Tools</guibutton> -> <guibutton>Options</guibutton> -> <guibutton>Advanced</guibutton> -> <guibutton>Network</guibutton> -><guibutton>Connection</guibutton> -> <guibutton>Settings</guibutton>
<literallayout>
<guibutton>Tools</guibutton> -> <guibutton>Options</guibutton> -> <guibutton>Advanced</guibutton> -> <guibutton>Network</guibutton> -><guibutton>Connection</guibutton> -> <guibutton>Settings</guibutton>
<literallayout>
<guibutton>Edit</guibutton> -> <guibutton>Preferences</guibutton> -> <guibutton>General</guibutton> -> <guibutton>Connection Settings</guibutton> -> <guibutton>Manual Proxy Configuration</guibutton>
<literallayout>
<guibutton>Edit</guibutton> -> <guibutton>Preferences</guibutton> -> <guibutton>General</guibutton> -> <guibutton>Connection Settings</guibutton> -> <guibutton>Manual Proxy Configuration</guibutton>
<!-- Mix ascii and gui art, something for everybody -->
<!-- spacing on this is tricky -->
<guibutton>Edit</guibutton> -> <guibutton>Preferences</guibutton> -> <guibutton>Advanced</guibutton> -> <guibutton>Proxies</guibutton> -> <guibutton>HTTP Proxy</guibutton>
<!-- Mix ascii and gui art, something for everybody -->
<!-- spacing on this is tricky -->
<guibutton>Edit</guibutton> -> <guibutton>Preferences</guibutton> -> <guibutton>Advanced</guibutton> -> <guibutton>Proxies</guibutton> -> <guibutton>HTTP Proxy</guibutton>
(shortcut: <ulink url="http://p.p/">http://p.p/</ulink>),
which is a built-in page and works without Internet access.
You will see the following section:
(shortcut: <ulink url="http://p.p/">http://p.p/</ulink>),
which is a built-in page and works without Internet access.
You will see the following section:
</para>
<!-- Needs to be put in a table and colorized -->
</para>
<!-- Needs to be put in a table and colorized -->
following patterns</quote>, and <literal>-block</literal> means <quote>don't
block URLs that match the following patterns, even if <literal>+block</literal>
previously applied.</quote>
following patterns</quote>, and <literal>-block</literal> means <quote>don't
block URLs that match the following patterns, even if <literal>+block</literal>
previously applied.</quote>
# Alias for specific file types that are text, but might have conflicting
# MIME types. We want the browser to force these to be text documents.
handle-as-text = -<link linkend="FILTER">filter</link> +-<link linkend="content-type-overwrite">content-type-overwrite{text/plain}</link> +-<link linkend="FORCE-TEXT-MODE">force-text-mode</link> -<link linkend="HIDE-CONTENT-DISPOSITION">hide-content-disposition</link></screen>
# Alias for specific file types that are text, but might have conflicting
# MIME types. We want the browser to force these to be text documents.
handle-as-text = -<link linkend="FILTER">filter</link> +-<link linkend="content-type-overwrite">content-type-overwrite{text/plain}</link> +-<link linkend="FORCE-TEXT-MODE">force-text-mode</link> -<link linkend="HIDE-CONTENT-DISPOSITION">hide-content-disposition</link></screen>
rules and other configuration options, and even turn
<application>Privoxy's</application> filtering off, all with
a web browser.
rules and other configuration options, and even turn
<application>Privoxy's</application> filtering off, all with
a web browser.
And finally we pull it all together in the bottom section and summarize how
<application>Privoxy</application> is applying all its <quote>actions</quote>
to <quote>google.com</quote>:
And finally we pull it all together in the bottom section and summarize how
<application>Privoxy</application> is applying all its <quote>actions</quote>
to <quote>google.com</quote>:
Final results:
-add-header
Final results:
-add-header
{ +block{Domains starts with "ad"} }
ad*.
{ +block{Domains starts with "ad"} }
ad*.
Matches for http://www.example.net/adsl/HOWTO/:
In file: default.action <guibutton>[ View ]</guibutton> <guibutton>[ Edit ]</guibutton>
Matches for http://www.example.net/adsl/HOWTO/:
In file: default.action <guibutton>[ View ]</guibutton> <guibutton>[ Edit ]</guibutton>
{ -block }
/adsl
</screen>
{ -block }
/adsl
</screen>
{ +block{Path starts with "ads".} +handle-as-image }
/ads
</screen>
{ +block{Path starts with "ads".} +handle-as-image }
/ads
</screen>
{ shop }
.quietpc.com
.worldpay.com # for quietpc.com
{ shop }
.quietpc.com
.worldpay.com # for quietpc.com
<quote><literal>{ shop }</literal></quote> is an <quote>alias</quote> that expands to
<quote><literal>{ -filter -session-cookies-only }</literal></quote>.
Or you could do your own exception to negate filtering:
<quote><literal>{ shop }</literal></quote> is an <quote>alias</quote> that expands to
<quote><literal>{ -filter -session-cookies-only }</literal></quote>.
Or you could do your own exception to negate filtering:
{ -filter }
# Disable ALL filter actions for sites in this section
.forbes.com
{ -filter }
# Disable ALL filter actions for sites in this section
.forbes.com
{ fragile }
# Handle with care: easy to break
mail.google.
{ fragile }
# Handle with care: easy to break
mail.google.