4 >Privoxy Configuration</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy User Manual"
10 HREF="index.html"><LINK
12 TITLE="Starting Privoxy"
13 HREF="startup.html"><LINK
15 TITLE="The Main Configuration File"
16 HREF="config.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy User Manual</TH
82 > configuration is stored
83 in text files. These files can be edited with a text editor.
84 Many important aspects of <SPAN
88 also be controlled easily with a web browser.
96 >6.1. Controlling <SPAN
99 > with Your Web Browser</A
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
137 HREF="http://config.privoxy.org/show-status"
139 >View & change the current configuration</A
146 HREF="http://config.privoxy.org/show-version"
148 >View the source code version numbers</A
155 HREF="http://config.privoxy.org/show-request"
157 >View the request headers.</A
164 HREF="http://config.privoxy.org/show-url-info"
166 >Look up which actions apply to a URL and why</A
173 HREF="http://config.privoxy.org/toggle"
175 >Toggle Privoxy on or off</A
188 > This should be self-explanatory. Note the first item leads to an editor for the
190 HREF="actions-file.html"
192 >, which is where the ad, banner,
193 cookie, and URL blocking magic is configured as well as other advanced features of
197 >. This is an easy way to adjust various
201 > configuration. The actions
202 file, and other configuration files, are explained in detail below. </P
206 >"Toggle Privoxy On or Off"</SPAN
207 > is handy for sites that might
208 have problems with your current actions and filters. You can in fact use
209 it as a test to see whether it is <SPAN
213 causing the problem or not. <SPAN
217 to run as a proxy in this case, but all manipulation is disabled, i.e.
221 > acts like a normal forwarding proxy. There
223 HREF="appendix.html#BOOKMARKLETS"
226 that you can toggle <SPAN
229 > with one click from
238 >6.2. Configuration Files Overview</A
241 > For Unix, *BSD and Linux, all configuration files are located in
245 > by default. For MS Windows, OS/2, and
246 AmigaOS these are all in the same directory as the
250 > executable. The name
251 and number of configuration files has changed from previous versions, and is
252 subject to change as development progresses.</P
254 > The installed defaults provide a reasonable starting point, though
255 some settings may be aggressive by some standards. For the time being, the
256 principle configuration files are:</P
265 >main configuration file</A
270 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
274 on Windows. This is a required file.
283 HREF="actions-file.html"
286 is used to define which <SPAN
289 > relating to banner-blocking, images, pop-ups,
290 content modification, cookie handling etc should be applied by default. It also defines many
291 exceptions (both positive and negative) from this default set of actions that enable
295 > to selectively eliminate the junk, and only the junk, on
296 as many websites as possible.
299 > Multiple actions files may be defined in <TT
303 are processed in the order they are defined. Local customizations and locally
304 preferred exceptions to the default policies as defined in
308 > (which you will most probably want
309 to define sooner or later) are probably best applied in
313 >, where you can preserve them across
325 There is also a web based editor that can be accessed from
327 HREF="http://config.privoxy.org/show-status"
329 >http://config.privoxy.org/show-status</A
332 HREF="http://p.p/show-status"
334 >http://p.p/show-status</A
336 various actions files.
345 HREF="filter-file.html"
348 >) can be used to re-write the raw page content, including
349 viewable text as well as embedded HTML and JavaScript, and whatever else
350 lurks on any given web page. The filtering jobs are only pre-defined here;
351 whether to apply them or not is up to the actions files.
357 > All files use the <SPAN
363 > character to denote a
364 comment (the rest of the line will be ignored) and understand line continuation
365 through placing a backslash ("<TT
368 >") as the very last character
369 in a line. If the <TT
372 > is preceded by a backslash, it looses
373 its special function. Placing a <TT
376 > in front of an otherwise
377 valid configuration line to prevent it from being interpreted is called "commenting
380 > The actions files and <TT
384 can use Perl style <A
385 HREF="appendix.html#REGEX"
386 >regular expressions</A
388 maximum flexibility. </P
390 > After making any changes, there is no need to restart
394 > in order for the changes to take
398 > detects such changes
399 automatically. Note, however, that it may take one or two additional
400 requests for the change to take effect. When changing the listening address
408 must obviously be sent to the <I
411 > listening address.</P
413 > While under development, the configuration content is subject to change.
414 The below documentation may not be accurate by the time you read this.
415 Also, what constitutes a <SPAN
418 > setting, may change, so
419 please check all your configuration files on important issues.</P
475 >The Main Configuration File</TD