<!entity copyright SYSTEM "copyright.sgml">
<!entity license SYSTEM "license.sgml">
<!entity p-version "3.0.7">
-<!entity p-status "UNRELEASED">
+<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
<!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 2.31 2007/11/05 02:34:53 hal9 Exp $
+ $Id: faq.sgml,v 2.32 2007/11/13 03:03:42 hal9 Exp $
Copyright (C) 2001-2007 Privoxy Developers http://privoxy.org
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: faq.sgml,v 2.31 2007/11/05 02:34:53 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 2.32 2007/11/13 03:03:42 hal9 Exp $</pubdate>
<!--
</para>
<para>
On the other hand, if you use non-Microsoft products, and you occasionally
- notice wierd characters on pages, you might want to try it.
+ notice weird characters on pages, you might want to try it.
</para>
</sect2>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
$Log: faq.sgml,v $
+Revision 2.32 2007/11/13 03:03:42 hal9
+Various changes to reflect new features and revised configuration for the
+upcoming release.
+
Revision 2.31 2007/11/05 02:34:53 hal9
Various changes in preparation for the upcoming release. Much yet to be done.
<!entity p-authors SYSTEM "p-authors.sgml">
<!entity config SYSTEM "p-config.sgml">
<!entity p-version "3.0.7">
-<!entity p-status "UNRELEASED">
+<!entity p-status "beta">
<!entity % p-authors-formal "INCLUDE"> <!-- include additional text, etc -->
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 2.42 2007/11/12 03:32:40 hal9 Exp $
+ $Id: user-manual.sgml,v 2.43 2007/11/14 18:45:39 fabiankeil Exp $
Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: user-manual.sgml,v 2.42 2007/11/12 03:32:40 hal9 Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 2.43 2007/11/14 18:45:39 fabiankeil Exp $</pubdate>
<!--
that can be used to create arbitrary <quote>tags</quote>
based on client and server headers.
These <quote>tags</quote> can then subsequently be used
- to control the actions used for the current request,
- greatly increasing &my-app;'s flexibity and selectivity. See <link
+ to control the other actions used for the current request,
+ greatly increasing &my-app;'s flexibility and selectivity. See <link
linkend="tag-pattern">tag patterns</link> for more information on tags.
</para>
</listitem>
Header filtering is done with dedicated header filters now. As a result
the actions <quote>filter-client-headers</quote> and <quote>filter-server-headers</quote>
that were introduced with <application>Privoxy 3.0.5</application> to apply
- the content filters to the headers as well have been removed again.
+ content filters to the headers have been removed.
See the new actions <link
linkend="server-header-filter">server-header-filter</link>
and <link
<para>
<link
linkend="templdir">templdir</link>
- to designate an alternate location for Privoxy's own CGI templates
- to make sure any locally customized templates aren't overwritten
- during upgrades.
+ to designate an alternate location for &my-app;'s
+ locally customized CGI templates so that
+ these are not overwritten during upgrades.
</para>
</listitem>
</itemizedlist>
linkend="forward-override">forward-override</link> action
allows changing of the forwarding settings through the actions files.
Combined with tags, this allows to choose the forwarder based on
- client headers like the User-Agent, or the request origin.
+ client headers like the <literal>User-Agent</literal>, or the request origin.
</para>
</listitem>
<listitem>
<para>
Many bugfixes, memory leaks addressed, code improvements, and logging
- improvments.
+ improvements.
</para>
</listitem>
<para>
The <quote>filter-client-headers</quote> and
<quote>filter-server-headers</quote> actions that were introduced with
- <application>Privoxy 3.0.5</application> to apply the content filters to
- the headers as, well have been removed and replaced with new actions.
+ <application>Privoxy 3.0.5</application> to apply content filters to
+ the headers have been removed and replaced with new actions.
See the <link
linkend="whatsnew">What's New section</link> above.
</para>
using our browser-based editor, which can be reached from <ulink
url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
Note: the config file option <link
- linkend="enable-edit-actions">enale-edit-actions</link> must be enabled for
+ linkend="enable-edit-actions">enable-edit-actions</link> must be enabled for
this to work. The editor allows both fine-grained control over every single
feature on a per-URL basis, and easy choosing from wholesale sets of defaults
like <quote>Cautious</quote>, <quote>Medium</quote> or
can tell them apart from URL patterns. Everything after the colon
including white space, is interpreted as a regular expression with
path pattern syntax, except that tag patterns aren't left-anchored
- automatically (Privoxy doesn't silently add a <quote>^</quote>,
+ automatically (&my-app; doesn't silently add a <quote>^</quote>,
you have to do it yourself if you need it).
</para>
</para>
<para>
- For example you could tag client requests which use the POST method,
- use this tag to activate another tagger that adds a tag if cookies
- are send, and then block based on the cookie tag. However if you'd
- reverse the position of the described taggers, and activated the method
- tagger based on the cookie tagger, no method tags would be created.
+ For example you could tag client requests which use the
+ <literal>POST</literal> method,
+ then use this tag to activate another tagger that adds a tag if cookies
+ are sent, and then use a block action based on the cookie tag. This allows
+ the outcome of one action, to be input into a subsequent action. However if
+ you'd reverse the position of the described taggers, and activated the
+ method tagger based on the cookie tagger, no method tags would be created.
The method tagger would look for the request line, but at the time
- the cookie tag is created the request line has already been parsed.
+ the cookie tag is created, the request line has already been parsed.
</para>
<para>
<literal><link linkend="client-header-tagger">client-header-tagger</link></literal>
and
<literal><link linkend="server-header-tagger">server-header-tagger</link></literal>.
- Taggers and filters use the same syntax in the filter files, the differnce
+ Taggers and filters use the same syntax in the filter files, the difference
is that taggers don't modify the text they are filtering, but use a rewritten
version of the filtered text as tag. The tags can then be used to change the
applying actions through sections with <link linkend="tag-pattern">tag-patterns</link>.
USA
$Log: user-manual.sgml,v $
+ Revision 2.43 2007/11/14 18:45:39 fabiankeil
+ - Mention some more contributors in the "New in this Release" list.
+ - Minor rewordings.
+
Revision 2.42 2007/11/12 03:32:40 hal9
Updates for "What's New" and "Notes to Upgraders". Various other changes in
preparation for new release. User Manual is almost ready.
projects / privoxy.git / commitdiff