4 >Privoxy Configuration</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.0 User Manual"
11 HREF="index.html"><LINK
13 TITLE="Starting Privoxy"
14 HREF="startup.html"><LINK
16 TITLE="The Main Configuration File"
17 HREF="config.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.0 User Manual</TH
76 NAME="CONFIGURATION">6. <SPAN
84 > configuration is stored
85 in text files. These files can be edited with a text editor.
86 Many important aspects of <SPAN
90 also be controlled easily with a web browser.
97 NAME="AEN579">6.1. Controlling <SPAN
100 > with Your Web Browser</H2
105 >'s user interface can be reached through the special
107 HREF="http://config.privoxy.org/"
109 >http://config.privoxy.org/</A
116 which is a built-in page and works without Internet access.
117 You will see the following section: </P
129 NAME="AEN588"> Privoxy Menu</H2
138 HREF="http://config.privoxy.org/show-status"
140 >View & change the current configuration</A
147 HREF="http://config.privoxy.org/show-version"
149 >View the source code version numbers</A
156 HREF="http://config.privoxy.org/show-request"
158 >View the request headers.</A
165 HREF="http://config.privoxy.org/show-url-info"
167 >Look up which actions apply to a URL and why</A
174 HREF="http://config.privoxy.org/toggle"
176 >Toggle Privoxy on or off</A
183 HREF="http://www.privoxy.org/3.0.0/user-manual/"
198 > This should be self-explanatory. Note the first item leads to an editor for the
200 HREF="actions-file.html"
202 >, which is where the ad, banner,
203 cookie, and URL blocking magic is configured as well as other advanced features of
207 >. This is an easy way to adjust various
211 > configuration. The actions
212 file, and other configuration files, are explained in detail below. </P
216 >"Toggle Privoxy On or Off"</SPAN
217 > is handy for sites that might
218 have problems with your current actions and filters. You can in fact use
219 it as a test to see whether it is <SPAN
223 causing the problem or not. <SPAN
227 to run as a proxy in this case, but all manipulation is disabled, i.e.
231 > acts like a normal forwarding proxy. There
233 HREF="appendix.html#BOOKMARKLETS"
236 that you can toggle <SPAN
239 > with one click from
247 NAME="CONFOVERVIEW">6.2. Configuration Files Overview</H2
249 > For Unix, *BSD and Linux, all configuration files are located in
253 > by default. For MS Windows, OS/2, and
254 AmigaOS these are all in the same directory as the
260 > The installed defaults provide a reasonable starting point, though
261 some settings may be aggressive by some standards. For the time being, the
262 principle configuration files are:</P
271 >main configuration file</A
276 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
280 on Windows. This is a required file.
289 HREF="actions-file.html"
292 is used to define which <SPAN
295 > relating to banner-blocking, images, pop-ups,
296 content modification, cookie handling etc should be applied by default. It also defines many
297 exceptions (both positive and negative) from this default set of actions that enable
301 > to selectively eliminate the junk, and only the junk, on
302 as many websites as possible.
305 > Multiple actions files may be defined in <TT
309 are processed in the order they are defined. Local customizations and locally
310 preferred exceptions to the default policies as defined in
314 > (which you will most probably want
315 to define sooner or later) are probably best applied in
319 >, where you can preserve them across
331 There is also a web based editor that can be accessed from
333 HREF="http://config.privoxy.org/show-status"
335 >http://config.privoxy.org/show-status</A
338 HREF="http://p.p/show-status"
340 >http://p.p/show-status</A
342 various actions files.
351 HREF="filter-file.html"
354 >) can be used to re-write the raw page content, including
355 viewable text as well as embedded HTML and JavaScript, and whatever else
356 lurks on any given web page. The filtering jobs are only pre-defined here;
357 whether to apply them or not is up to the actions files.
363 > All files use the <SPAN
369 > character to denote a
370 comment (the rest of the line will be ignored) and understand line continuation
371 through placing a backslash ("<TT
374 >") as the very last character
375 in a line. If the <TT
378 > is preceded by a backslash, it looses
379 its special function. Placing a <TT
382 > in front of an otherwise
383 valid configuration line to prevent it from being interpreted is called "commenting
386 > The actions files and <TT
390 can use Perl style <A
391 HREF="appendix.html#REGEX"
392 >regular expressions</A
394 maximum flexibility. </P
396 > After making any changes, there is no need to restart
400 > in order for the changes to take
404 > detects such changes
405 automatically. Note, however, that it may take one or two additional
406 requests for the change to take effect. When changing the listening address
414 must obviously be sent to the <SPAN
420 > listening address.</P
428 SUMMARY="Footer navigation table"
480 >The Main Configuration File</TD