4 >Privoxy Configuration</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy 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
39 >Privoxy User Manual</TH
83 > configuration is stored
84 in text files. These files can be edited with a text editor.
85 Many important aspects of <SPAN
89 also be controlled easily with a web browser.
97 >6.1. Controlling <SPAN
100 > with Your Web Browser</A
106 >'s user interface can be reached through the special
108 HREF="http://config.privoxy.org/"
110 >http://config.privoxy.org/</A
117 which is a built-in page and works without Internet access.
118 You will see the following section: </P
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
189 > This should be self-explanatory. Note the first item leads to an editor for the
191 HREF="actions-file.html"
193 >, which is where the ad, banner,
194 cookie, and URL blocking magic is configured as well as other advanced features of
198 >. This is an easy way to adjust various
202 > configuration. The actions
203 file, and other configuration files, are explained in detail below. </P
207 >"Toggle Privoxy On or Off"</SPAN
208 > is handy for sites that might
209 have problems with your current actions and filters. You can in fact use
210 it as a test to see whether it is <SPAN
214 causing the problem or not. <SPAN
218 to run as a proxy in this case, but all manipulation is disabled, i.e.
222 > acts like a normal forwarding proxy. There
224 HREF="appendix.html#BOOKMARKLETS"
227 that you can toggle <SPAN
230 > with one click from
239 >6.2. Configuration Files Overview</A
242 > For Unix, *BSD and Linux, all configuration files are located in
246 > by default. For MS Windows, OS/2, and
247 AmigaOS these are all in the same directory as the
251 > executable. The name
252 and number of configuration files has changed from previous versions, and is
253 subject to change as development progresses.</P
255 > The installed defaults provide a reasonable starting point, though
256 some settings may be aggressive by some standards. For the time being, the
257 principle configuration files are:</P
266 >main configuration file</A
271 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
275 on Windows. This is a required file.
284 HREF="actions-file.html"
287 is used to define which <SPAN
290 > relating to banner-blocking, images, pop-ups,
291 content modification, cookie handling etc should be applied by default. It also defines many
292 exceptions (both positive and negative) from this default set of actions that enable
296 > to selectively eliminate the junk, and only the junk, on
297 as many websites as possible.
300 > Multiple actions files may be defined in <TT
304 are processed in the order they are defined. Local customizations and locally
305 preferred exceptions to the default policies as defined in
309 > (which you will most propably want
310 to define sooner or later) are probably best applied in
314 >, where you can preserve them across
326 There is also a web based editor that can be accessed from
328 HREF="http://config.privoxy.org/show-status"
330 >http://config.privoxy.org/show-status</A
333 HREF="http://p.p/show-status"
335 >http://p.p/show-status</A
337 various actions files.
346 HREF="filter-file.html"
349 >) can be used to re-write the raw page content, including
350 viewable text as well as embedded HTML and JavaScript, and whatever else
351 lurks on any given web page. The filtering jobs are only pre-defined here;
352 whether to apply them or not is up to the actions files.
358 > All files use the <SPAN
364 > character to denote a
365 comment (the rest of the line will be ignored) and understand line continuation
366 through placing a backslash ("<TT
369 >") as the very last character
370 in a line. If the <TT
373 > is preceded by a backslash, it looses
374 its special function. Placing a <TT
377 > in front of an otherwise
378 valid configuration line to prevent it from being interpreted is called "commenting
381 > The actions files and <TT
385 can use Perl style <A
386 HREF="appendix.html#REGEX"
387 >regular expressions</A
389 maximum flexibility. </P
391 > After making any changes, there is no need to restart
395 > in order for the changes to take
399 > detects such changes
400 automatically. Note, however, that it may take one or two additional
401 requests for the change to take effect. When changing the listening address
409 must obviously be sent to the <I
412 > listening address.</P
414 > While under development, the configuration content is subject to change.
415 The below documentation may not be accurate by the time you read this.
416 Also, what constitutes a <SPAN
419 > setting, may change, so
420 please check all your configuration files on important issues.</P
476 >The Main Configuration File</TD