4 >Privoxy Configuration</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.4 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
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.4 User Manual</TH
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.
103 >6.1. Controlling <SPAN
106 > with Your Web Browser</H2
111 >'s user interface can be reached through the special
113 HREF="http://config.privoxy.org/"
115 >http://config.privoxy.org/</A
122 which is a built-in page and works without Internet access.
123 You will see the following section: </P
146 HREF="http://config.privoxy.org/show-status"
148 >View & change the current configuration</A
155 HREF="http://config.privoxy.org/show-version"
157 >View the source code version numbers</A
164 HREF="http://config.privoxy.org/show-request"
166 >View the request headers.</A
173 HREF="http://config.privoxy.org/show-url-info"
175 >Look up which actions apply to a URL and why</A
182 HREF="http://config.privoxy.org/toggle"
184 >Toggle Privoxy on or off</A
191 HREF="http://www.privoxy.org/ 3.0.4/user-manual/"
206 > This should be self-explanatory. Note the first item leads to an editor for the
208 HREF="actions-file.html"
210 >, which is where the ad, banner,
211 cookie, and URL blocking magic is configured as well as other advanced features of
215 >. This is an easy way to adjust various
219 > configuration. The actions
220 file, and other configuration files, are explained in detail below. </P
224 >"Toggle Privoxy On or Off"</SPAN
225 > is handy for sites that might
226 have problems with your current actions and filters. You can in fact use
227 it as a test to see whether it is <SPAN
231 causing the problem or not. <SPAN
235 to run as a proxy in this case, but all manipulation is disabled, i.e.
239 > acts like a normal forwarding proxy. There
241 HREF="appendix.html#BOOKMARKLETS"
244 that you can toggle <SPAN
247 > with one click from
257 >6.2. Configuration Files Overview</H2
259 > For Unix, *BSD and Linux, all configuration files are located in
263 > by default. For MS Windows, OS/2, and
264 AmigaOS these are all in the same directory as the
268 > executable. The name
269 and number of configuration files has changed from previous versions, and is
270 subject to change as development progresses.</P
272 > The installed defaults provide a reasonable starting point, though
273 some settings may be aggressive by some standards. For the time being, the
274 principle configuration files are:</P
283 >main configuration file</A
288 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
292 on Windows. This is a required file.
301 HREF="actions-file.html"
304 is used to define which <SPAN
307 > relating to banner-blocking, images, pop-ups,
308 content modification, cookie handling etc should be applied by default. It also defines many
309 exceptions (both positive and negative) from this default set of actions that enable
313 > to selectively eliminate the junk, and only the junk, on
314 as many websites as possible.
317 > Multiple actions files may be defined in <TT
321 are processed in the order they are defined. Local customizations and locally
322 preferred exceptions to the default policies as defined in
326 > (which you will most probably want
327 to define sooner or later) are probably best applied in
331 >, where you can preserve them across
343 There is also a web based editor that can be accessed from
345 HREF="http://config.privoxy.org/show-status"
347 >http://config.privoxy.org/show-status</A
350 HREF="http://p.p/show-status"
352 >http://p.p/show-status</A
354 various actions files.
361 >"Filter files"</SPAN
363 HREF="filter-file.html"
366 >) can be used to re-write the raw page content, including
367 viewable text as well as embedded HTML and JavaScript, and whatever else
368 lurks on any given web page. The filtering jobs are only pre-defined here;
369 whether to apply them or not is up to the actions files.
373 > includes various filters made
374 available for use by the developers. Some are much more intrusive than
375 others, and all should be used with caution. You may define additional
380 actions files. We suggest <TT
384 locally defined filters or customizations.
390 > The syntax of all configuration files has remained the same throughout the
391 3.x series. There have been enhancements, but no changes that would preclude
392 the use of any configuration file from one version to the next.</P
394 > All files use the <SPAN
400 > character to denote a
401 comment (the rest of the line will be ignored) and understand line continuation
402 through placing a backslash ("<TT
405 >") as the very last character
406 in a line. If the <TT
409 > is preceded by a backslash, it looses
410 its special function. Placing a <TT
413 > in front of an otherwise
414 valid configuration line to prevent it from being interpreted is called "commenting
417 > The actions files and filter files
418 can use Perl style <A
419 HREF="appendix.html#REGEX"
420 >regular expressions</A
422 maximum flexibility. </P
424 > After making any changes, there is no need to restart
428 > in order for the changes to take
432 > detects such changes
433 automatically. Note, however, that it may take one or two additional
434 requests for the change to take effect. When changing the listening address
442 must obviously be sent to the <SPAN
448 > listening address.</P
450 > While under development, the configuration content is subject to change.
451 The below documentation may not be accurate by the time you read this.
452 Also, what constitutes a <SPAN
455 > setting, may change, so
456 please check all your configuration files on important issues.</P
464 SUMMARY="Footer navigation table"
516 >The Main Configuration File</TD