1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Privoxy Configuration</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy 3.0.14 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"><META
21 HTTP-EQUIV="Content-Type"
24 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
36 SUMMARY="Header navigation table"
45 >Privoxy 3.0.14 User Manual</TH
82 >6. Privoxy Configuration</A
88 > configuration is stored
89 in text files. These files can be edited with a text editor.
90 Many important aspects of <SPAN
94 also be controlled easily with a web browser.
102 >6.1. Controlling Privoxy with Your Web Browser</A
108 >'s user interface can be reached through the special
110 HREF="http://config.privoxy.org/"
112 >http://config.privoxy.org/</A
119 which is a built-in page and works without Internet access.
120 You will see the following section: </P
143 HREF="http://config.privoxy.org/show-status"
145 >View & change the current configuration</A
152 HREF="http://config.privoxy.org/show-version"
154 >View the source code version numbers</A
161 HREF="http://config.privoxy.org/show-request"
163 >View the request headers.</A
170 HREF="http://config.privoxy.org/show-url-info"
172 >Look up which actions apply to a URL and why</A
179 HREF="http://config.privoxy.org/toggle"
181 >Toggle Privoxy on or off</A
188 HREF="http://www.privoxy.org/3.0.14/user-manual/"
203 > This should be self-explanatory. Note the first item leads to an editor for the
205 HREF="actions-file.html"
207 >, which is where the ad, banner,
208 cookie, and URL blocking magic is configured as well as other advanced features of
212 >. This is an easy way to adjust various
216 > configuration. The actions
217 file, and other configuration files, are explained in detail below. </P
221 >"Toggle Privoxy On or Off"</SPAN
222 > is handy for sites that might
223 have problems with your current actions and filters. You can in fact use
224 it as a test to see whether it is <SPAN
228 causing the problem or not. <SPAN
232 to run as a proxy in this case, but all manipulation is disabled, i.e.
236 > acts like a normal forwarding proxy. There
238 HREF="appendix.html#BOOKMARKLETS"
241 that you can toggle <SPAN
244 > with one click from
247 > Note that several of the features described above are disabled by default
251 > 3.0.7 beta and later.
256 >configuration file</A
258 and in which cases it's safe to enable them again.</P
266 >6.2. Configuration Files Overview</A
269 > For Unix, *BSD and Linux, all configuration files are located in
273 > by default. For MS Windows, OS/2, and
274 AmigaOS these are all in the same directory as the
278 > executable. The name
279 and number of configuration files has changed from previous versions, and is
280 subject to change as development progresses.</P
282 > The installed defaults provide a reasonable starting point, though
283 some settings may be aggressive by some standards. For the time being, the
284 principle configuration files are:</P
293 >main configuration file</A
298 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
302 on Windows. This is a required file.
309 >match-all.action</TT
310 > is used to define which <SPAN
314 relating to banner-blocking, images, pop-ups, content modification, cookie handling
315 etc should be applied by default. It should be the first actions file loaded.
321 > defines many exceptions (both positive and negative)
322 from the default set of actions that's configured in <TT
324 >match-all.action</TT
326 It should be the second actions file loaded and shouldn't be edited by the user.
329 > Multiple actions files may be defined in <TT
333 are processed in the order they are defined. Local customizations and locally
334 preferred exceptions to the default policies as defined in
337 >match-all.action</TT
338 > (which you will most probably want
339 to define sooner or later) are best applied in <TT
343 where you can preserve them across upgrades. The file isn't installed by all
344 installers, but you can easily create it yourself with a text editor.
348 There is also a web based editor that can be accessed from
350 HREF="http://config.privoxy.org/show-status"
352 >http://config.privoxy.org/show-status</A
355 HREF="http://p.p/show-status"
357 >http://p.p/show-status</A
359 various actions files.
366 >"Filter files"</SPAN
368 HREF="filter-file.html"
371 >) can be used to re-write the raw page content, including
372 viewable text as well as embedded HTML and JavaScript, and whatever else
373 lurks on any given web page. The filtering jobs are only pre-defined here;
374 whether to apply them or not is up to the actions files.
378 > includes various filters made
379 available for use by the developers. Some are much more intrusive than
380 others, and all should be used with caution. You may define additional
385 actions files. We suggest <TT
389 locally defined filters or customizations.
395 > The syntax of the configuration and filter files may change between different
396 Privoxy versions, unfortunately some enhancements cost backwards compatibility.
399 > All files use the <SPAN
405 > character to denote a
406 comment (the rest of the line will be ignored) and understand line continuation
407 through placing a backslash ("<TT
410 >") as the very last character
411 in a line. If the <TT
414 > is preceded by a backslash, it looses
415 its special function. Placing a <TT
418 > in front of an otherwise
419 valid configuration line to prevent it from being interpreted is called "commenting
420 out" that line. Blank lines are ignored.</P
422 > The actions files and filter files
423 can use Perl style <A
424 HREF="appendix.html#REGEX"
425 >regular expressions</A
427 maximum flexibility. </P
429 > After making any changes, there is no need to restart
433 > in order for the changes to take
437 > detects such changes
438 automatically. Note, however, that it may take one or two additional
439 requests for the change to take effect. When changing the listening address
447 must obviously be sent to the <SPAN
453 > listening address.</P
455 > While under development, the configuration content is subject to change.
456 The below documentation may not be accurate by the time you read this.
457 Also, what constitutes a <SPAN
460 > setting, may change, so
461 please check all your configuration files on important issues.</P
469 SUMMARY="Footer navigation table"
508 >Starting Privoxy</TD
518 >The Main Configuration File</TD