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
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.4 User Manual</TH
86 > configuration is stored
87 in text files. These files can be edited with a text editor.
88 Many important aspects of <SPAN
92 also be controlled easily with a web browser.
101 >6.1. Controlling <SPAN
104 > with Your Web Browser</H2
109 >'s user interface can be reached through the special
111 HREF="http://config.privoxy.org/"
113 >http://config.privoxy.org/</A
120 which is a built-in page and works without Internet access.
121 You will see the following section: </P
144 HREF="http://config.privoxy.org/show-status"
146 >View & change the current configuration</A
153 HREF="http://config.privoxy.org/show-version"
155 >View the source code version numbers</A
162 HREF="http://config.privoxy.org/show-request"
164 >View the request headers.</A
171 HREF="http://config.privoxy.org/show-url-info"
173 >Look up which actions apply to a URL and why</A
180 HREF="http://config.privoxy.org/toggle"
182 >Toggle Privoxy on or off</A
189 HREF="http://www.privoxy.org/ 3.0.4/user-manual/"
204 > This should be self-explanatory. Note the first item leads to an editor for the
206 HREF="actions-file.html"
208 >, which is where the ad, banner,
209 cookie, and URL blocking magic is configured as well as other advanced features of
213 >. This is an easy way to adjust various
217 > configuration. The actions
218 file, and other configuration files, are explained in detail below. </P
222 >"Toggle Privoxy On or Off"</SPAN
223 > is handy for sites that might
224 have problems with your current actions and filters. You can in fact use
225 it as a test to see whether it is <SPAN
229 causing the problem or not. <SPAN
233 to run as a proxy in this case, but all manipulation is disabled, i.e.
237 > acts like a normal forwarding proxy. There
239 HREF="appendix.html#BOOKMARKLETS"
242 that you can toggle <SPAN
245 > with one click from
255 >6.2. Configuration Files Overview</H2
257 > For Unix, *BSD and Linux, all configuration files are located in
261 > by default. For MS Windows, OS/2, and
262 AmigaOS these are all in the same directory as the
266 > executable. The name
267 and number of configuration files has changed from previous versions, and is
268 subject to change as development progresses.</P
270 > The installed defaults provide a reasonable starting point, though
271 some settings may be aggressive by some standards. For the time being, the
272 principle configuration files are:</P
281 >main configuration file</A
286 on Linux, Unix, BSD, OS/2, and AmigaOS and <TT
290 on Windows. This is a required file.
299 HREF="actions-file.html"
302 is used to define which <SPAN
305 > relating to banner-blocking, images, pop-ups,
306 content modification, cookie handling etc should be applied by default. It also defines many
307 exceptions (both positive and negative) from this default set of actions that enable
311 > to selectively eliminate the junk, and only the junk, on
312 as many websites as possible.
315 > Multiple actions files may be defined in <TT
319 are processed in the order they are defined. Local customizations and locally
320 preferred exceptions to the default policies as defined in
324 > (which you will most probably want
325 to define sooner or later) are probably best applied in
329 >, where you can preserve them across
341 There is also a web based editor that can be accessed from
343 HREF="http://config.privoxy.org/show-status"
345 >http://config.privoxy.org/show-status</A
348 HREF="http://p.p/show-status"
350 >http://p.p/show-status</A
352 various actions files.
359 >"Filter files"</SPAN
361 HREF="filter-file.html"
364 >) can be used to re-write the raw page content, including
365 viewable text as well as embedded HTML and JavaScript, and whatever else
366 lurks on any given web page. The filtering jobs are only pre-defined here;
367 whether to apply them or not is up to the actions files.
371 > includes various filters made
372 available for use by the developers. Some are much more intrusive than
373 others, and all should be used with caution. You may define additional
378 actions files. We suggest <TT
382 locally defined filters or customizations.
388 > All files use the <SPAN
394 > character to denote a
395 comment (the rest of the line will be ignored) and understand line continuation
396 through placing a backslash ("<TT
399 >") as the very last character
400 in a line. If the <TT
403 > is preceded by a backslash, it looses
404 its special function. Placing a <TT
407 > in front of an otherwise
408 valid configuration line to prevent it from being interpreted is called "commenting
411 > The actions files and filter files
412 can use Perl style <A
413 HREF="appendix.html#REGEX"
414 >regular expressions</A
416 maximum flexibility. </P
418 > After making any changes, there is no need to restart
422 > in order for the changes to take
426 > detects such changes
427 automatically. Note, however, that it may take one or two additional
428 requests for the change to take effect. When changing the listening address
436 must obviously be sent to the <SPAN
442 > listening address.</P
444 > While under development, the configuration content is subject to change.
445 The below documentation may not be accurate by the time you read this.
446 Also, what constitutes a <SPAN
449 > setting, may change, so
450 please check all your configuration files on important issues.</P
458 SUMMARY="Footer navigation table"
510 >The Main Configuration File</TD