This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 2.29 2007/11/04 15:12:47 hal9 Exp $
+ $Id: faq.sgml,v 2.30 2007/11/04 15:16:40 hal9 Exp $
Copyright (C) 2001-2007 Privoxy Developers http://privoxy.org
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: faq.sgml,v 2.29 2007/11/04 15:12:47 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 2.30 2007/11/04 15:16:40 hal9 Exp $</pubdate>
<!--
at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
(Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
<quote><ulink url="http://config.privoxy.org/show-status">View &
- change the current configuration</ulink></quote> from the menu.
+ change the current configuration</ulink></quote> from the menu. Note
+ that this feature must be explicitly enabled in the main config file
+ (see <ulink
+ url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
</para>
</sect2>
There is no GUI editor option for this part of the configuration,
but you can disable/enable the various pre-defined filters of the included
<filename>default.filter</filename> file with the <ulink
- url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
+ url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>
+ Note
+ that the custom actions editor must be explicitly enabled in the main config file
+ (see <ulink
+ url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
+
</para>
</sect2>
<listitem><para>
<application>Privoxy</application> is not running. Solution: verify
that &my-app; is installed correctly, has not crashed, and is indeed running.
- Turn on <application>Privoxy's</application> logging and look at the logs to see what they say.
+ Turn on <application>Privoxy's</application> logging, and look at the logs to see what they say.
</para></listitem>
<listitem><para>Or your browser is configured for a different port than what
<application>Privoxy</application> is using. Solution: verify that &my-app;
entirely different from the site URL itself. Most ads are hosted on different
servers than the main site itself. If you right-click on the ad, you should
be able to get all the relevant information you need. Alternately, you can
- find the correct URL by looking at <application>Privoxy's</application> logs.
+ find the correct URL by looking at <application>Privoxy's</application> logs
+ (you may need to enable logging in the main config file if its disabled).
</para>
<para>
Below is a slightly modified real-life log snippet that originates with one
and paste the full URL of the page in question into the prompt. See which
actions are being applied to the URL, and which matches in which actions
files are responsible for that. It might be helpful also to look at your logs
- for this site too, to see what else might be happening. Many sites are
+ for this site too, to see what else might be happening (note: logging may need
+ to be enabled in the main config file). Many sites are
complex and require a number of related pages to help present their content.
Look at what else might be used by the page in question, and what of that
might be <emphasis>required</emphasis>.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
$Log: faq.sgml,v $
+Revision 2.30 2007/11/04 15:16:40 hal9
+Fix one silly typo.
+
Revision 2.29 2007/11/04 15:12:47 hal9
Various minor adjustments.
<!entity p-authors SYSTEM "p-authors.sgml">
<!entity config SYSTEM "p-config.sgml">
<!entity p-version "3.0.7">
-<!entity p-status "stable">
+<!entity p-status "UNRELEASED">
<!entity % p-authors-formal "INCLUDE"> <!-- include additional text, etc -->
-<!entity % p-not-stable "IGNORE">
-<!entity % p-stable "INCLUDE">
+<!entity % p-not-stable "INCLUDE">
+<!entity % p-stable "IGNORE">
<!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
<!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
<!entity % p-readme "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 2.37 2007/08/27 16:09:55 fabiankeil Exp $
+ $Id: user-manual.sgml,v 2.38 2007/09/22 16:01:42 fabiankeil Exp $
Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: user-manual.sgml,v 2.37 2007/08/27 16:09:55 fabiankeil Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 2.38 2007/09/22 16:01:42 fabiankeil Exp $</pubdate>
<!--
these features are incorporated into your configuration somehow.
</para>
</listitem>
+ <listitem>
+ <para>
+ <filename>standard.action</filename> now only includes the enabled actions.
+ Not all actions as before.
+ </para>
+ </listitem>
+ <!--
<listitem>
<para>
See the full documentation on
</para>
</listitem>
+ -->
+ <listitem>
+ <para>
+ Logging is off by default now. If you need logging, it can be turned on
+ in the <link linkend="logfile">config file</link>.
+ </para>
+ </listitem>
+
<listitem>
<para>
- The <filename>jarfile</filename>,
- <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookie</ulink> logger, is off by default now.
+ Three other config file settings are now off by default:
+ <link linkend="enable-remote-toggle">enable-remote-toggle</link>,
+ <link linkend="enable-remote-http-toggle">enable-remote-http-toggle</link>,
+ and <link linkend="enable-edit-actions">enable-edit-actions</link>.
+ If you use or want these, you will need to explicitly enable them, and
+ be aware of the security issues involved.
</para>
</listitem>
+<!--
<listitem>
<para>
What constitutes a <quote>default</quote> configuration has changed,
settings as yet (see above).
</para>
</listitem>
-
+-->
+<!--
<listitem>
<para>
The default actions setting is now <literal>Cautious</literal>. Previous
<listitem>
<para>
-<!-- I think it is best to keep this somewhat vague, in case -->
-<!-- the situation changes under our feet. -->
Some installers may not automatically start
<application>Privoxy</application> after installation.
</para>
</listitem>
-
+-->
</itemizedlist>
</para>
+
</sect2>
</sect1>
The easiest way to edit the actions files is with a browser by
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>.
- 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 <quote>Advanced</quote>.
- Warning: the <quote>Advanced</quote> setting is more aggressive, and
- will be more likely to cause problems for some sites. Experienced users only!
-</para>
+ Note: the config file option <link
+ linkend="enable-edit-actions">enale-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
+ <quote>Advanced</quote>. Warning: the <quote>Advanced</quote> setting is more
+ aggressive, and will be more likely to cause problems for some sites.
+ Experienced users only!
+ </para>
<para>
If you prefer plain text editing to GUIs, you can of course also directly edit the
<para>
<screen>
# Tag every request with the declared content type
-{+client-header-filter{content-type}}
+{+client-header-tagger{content-type}}
/
</screen>
</para>
USA
$Log: user-manual.sgml,v $
+ Revision 2.38 2007/09/22 16:01:42 fabiankeil
+ Update embedded show-url-info output.
+
Revision 2.37 2007/08/27 16:09:55 fabiankeil
- Fix --pre-chroot-nslookup description which I failed to
+ Fix pre-chroot-nslookup description which I failed to
copy and paste properly. Reported by Stephen Gildea.
Revision 2.36 2007/08/26 16:47:14 fabiankeil
- Add Stephen Gildea's --pre-chroot-nslookup patch [#1276666],
+ Add Stephen Gildea's pre-chroot-nslookup patch [#1276666],
extensive comments moved to user manual.
Revision 2.35 2007/08/26 14:59:49 fabiankeil