4 >Quickstart to Using Privoxy</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
14 HREF="installation.html"><LINK
16 TITLE="Privoxy Configuration"
17 HREF="configuration.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="installation.html"
60 HREF="configuration.html"
74 >4. Quickstart to Using <SPAN
85 >4.1. Note to Upgraders</A
88 > There are very significant changes from older versions of
96 >. Configuration is substantially
99 >Junkbuster 2.0.x</SPAN
101 configuration files will not migrate. The functionality of the old
112 >, are now combined into the
115 >"actions file"</SPAN
120 for most installations).</P
133 of the new sophistication (explained below). <TT
137 much the same as before.</P
139 > If upgrading from a 2.0.x version, you will have to use the new config
140 files, and possibly adapt any personal rules from your older files.
141 When porting personal rules over from the old <TT
145 to the new actions file, please note that even the pattern syntax has
146 changed. If upgrading from 2.9.x development versions, it is still
147 recommended to use the new configuration files.</P
149 > A quick list of things to be aware of before upgrading: </P
156 > The default listening port is now 8118 due to a conflict with another
163 Some installers may remove earlier versions completely. Save any
164 important configuration files!
172 > is controllable with a web browser
173 at the special URL: <A
174 HREF="http://config.privoxy.org/"
176 >http://config.privoxy.org/</A
183 aspects of configuration can be done here, including temporarily disabling
192 > The primary configuration file for cookie management, ad and banner
193 blocking, and many other aspects of <SPAN
201 recommended to become familiar with the new actions concept below,
202 before modifying this file.
208 Some installers may not automatically start
212 > after installation.
230 > Before launching <SPAN
233 > for the first time, you
234 will want to configure your browser(s) to use <SPAN
238 as a HTTP and HTTPS proxy. The default is localhost for the proxy address,
239 and port 8118 (earlier versions used port 8000). This is the one
240 configuration step that must be done! </P
250 >), this can be set under <TT
253 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</TT
257 >Internet Explorer</SPAN
261 Internet Properties -> Connections -> LAN Setting</TT
266 > and fill in the appropriate info (Address:
267 localhost, Port: 8118). Include if HTTPS proxy support too.</P
269 > After doing this, flush your browser's disk and memory caches to force a
270 re-reading of all pages and to get rid of any ads that may be cached. You
271 are now ready to start enjoying the benefits of using
280 > is typically started by specifying the
281 main configuration file to be used on the command line. Example Unix startup
293 # /usr/sbin/privoxy /etc/privoxy/config
302 HREF="quickstart.html#CMDOPTIONS"
304 > for other command line options.</P
306 > An init script is provided for SuSE and Red Hat.</P
313 > For Red Hat and Debian: <B
315 >/etc/rc.d/init.d/privoxy start</B
318 > If no configuration file is specified on the command line,
322 > will look for a file named
326 > in the current directory. Except on Win32 where
330 >. If no file is specified on the
331 command line and no default configuration file can be found,
335 > will fail to start.</P
337 > The included default configuration files should give a reasonable starting
338 point. Most of the per site configuration is done in the
342 > files. These are where various cookie actions are
343 defined, ad and banner blocking, and other aspects of
347 > configuration. There are several such
348 files included, with varying levels of aggressiveness. </P
350 > You will probably want to keep an eye out for sites that require persistent
351 cookies, and add these to <TT
355 default, most of these will be accepted only during the current browser
358 >"session cookies"</SPAN
359 >), until you add them to the
360 configuration. If you want the browser to handle this instead, you will need
364 > and disable this feature. If you
365 use more than one browser, it would make more sense to let
369 > handle this. In which case, the
370 browser(s) should be set to accept all cookies.</P
372 > Another feature where you will probably want to define exceptions for trusted
373 sites is the popup-killing (through the <TT
380 > actions), because your favorite shopping,
381 banking, or leisure site may need popups. </P
386 > is HTTP/1.1 compliant, but not all of
387 the optional 1.1 features are as yet supported. In the unlikely event that
388 you experience inexplicable problems with browsers that use HTTP/1.1 per default
392 > or recent versions of I.E.), you might
393 try to force HTTP/1.0 compatibility. For Mozilla, look under <TT
396 Preferences -> Debug -> Networking</TT
398 Alternatively, set the <SPAN
405 > which will downgrade your browser's HTTP
406 requests from HTTP/1.1 to HTTP/1.0 before processing them.</P
408 > After running <SPAN
411 > for a while, you can
412 start to fine tune the configuration to suit your personal, or site,
413 preferences and requirements. There are many, many aspects that can
417 > (as specified in <TT
421 can be adjusted by pointing your browser to
423 HREF="http://config.privoxy.org/"
425 >http://config.privoxy.org/</A
432 and then follow the link to <SPAN
434 >"edit the actions list"</SPAN
436 (This is an internal page and does not require Internet access.)</P
438 > In fact, various aspects of <SPAN
442 configuration can be viewed from this page, including
443 current configuration parameters, source code version numbers,
444 the browser's request headers, and <SPAN
448 to a given URL. In addition to the <TT
452 editor mentioned above, <SPAN
462 > (toggled) from this page.</P
464 > If you encounter problems, try loading the page without
468 >. If that helps, enter the URL where
469 you have the problems into <A
470 HREF="http://p.p/show-url-info"
473 based rule tracing utility</A
474 >. See which rules apply and why, and
475 then try turning them off for that site one after the other, until the problem
476 is gone. When you have found the culprit, you might want to turn the rest on
479 > If the above paragraph sounds gibberish to you, you might want to <A
480 HREF="configuration.html#ACTIONSFILE"
482 >read more about the actions concept</A
484 or even dive deep into the <A
485 HREF="appendix.html#ACTIONSANAT"
491 > If you can't get rid of the problem at all, think you've found a bug in
492 Privoxy, want to propose a new feature or smarter rules, please see the
493 chapter "Contacting the Developers, .." below.</P
501 >4.3. Command Line Options</A
507 > may be invoked with the following
508 command-line options:</P
521 > Print version info and exit. Unix only.
532 > Print short usage info and exit. Unix only.
543 > Don't become a daemon, i.e. don't fork and become process group
544 leader, and don't detach from controlling tty. Unix only.
556 > On startup, write the process ID to <I
563 > on exit. Failure to create or delete the
567 > is non-fatal. If no <I
571 option is given, no PID file will be used. Unix only.
578 >--user USER[.GROUP]</I
583 > After (optionally) writing the PID file, assume the user ID of
587 >, and if included the GID of GROUP. Exit if the
588 privileges are not sufficient to do so. Unix only.
602 > is included on the command line,
606 > will look for a file named
610 > in the current directory (except on Win32
611 where it will look for <SPAN
615 full path to avoid confusion. If no config file is found,
619 > will fail to start.
641 HREF="installation.html"
657 HREF="configuration.html"