4 >Starting Privoxy</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
13 TITLE="Quickstart to Using Privoxy"
14 HREF="quickstart.html"><LINK
16 TITLE="Privoxy Configuration"
17 HREF="configuration.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="quickstart.html"
60 HREF="configuration.html"
80 > Before launching <SPAN
83 > for the first time, you
84 will want to configure your browser(s) to use <SPAN
88 as a HTTP and HTTPS proxy. The default is localhost for the proxy address,
89 and port 8118 (earlier versions used port 8000). This is the one
90 configuration step that must be done! </P
100 >), this can be set under <TT
103 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</TT
107 >Internet Explorer</SPAN
111 Internet Properties -> Connections -> LAN Setting</TT
116 > and fill in the appropriate info (Address:
117 localhost, Port: 8118). Include if HTTPS proxy support too.</P
119 > After doing this, flush your browser's disk and memory caches to force a
120 re-reading of all pages and to get rid of any ads that may be cached. You
121 are now ready to start enjoying the benefits of using
130 > is typically started by specifying the
131 main configuration file to be used on the command line. Example Unix startup
143 # /usr/sbin/privoxy /etc/privoxy/config</PRE
150 HREF="startup.html#CMDOPTIONS"
152 > for other command line options.</P
154 > An init script is provided for SuSE and Red Hat.</P
161 > For Red Hat and Debian: <B
163 >/etc/rc.d/init.d/privoxy start</B
166 > If no configuration file is specified on the command line,
170 > will look for a file named
174 > in the current directory. Except on Win32 where
178 >. If no file is specified on the
179 command line and no default configuration file can be found,
183 > will fail to start.</P
185 > The included default configuration files should give a reasonable starting
186 point. Most of the per site configuration is done in the
190 > files. These are where various cookie actions are
191 defined, ad and banner blocking, and other aspects of
195 > configuration. There are several such
196 files included, with varying levels of aggressiveness. </P
198 > You will probably want to keep an eye out for sites for which you may prefer
199 persistent cookies, and add these to your actions configuration as needed. By
200 default, most of these will be accepted only during the current browser
203 >"session cookies"</SPAN
204 >), unless you add them to the
205 configuration. If you want the browser to handle this instead, you will need
209 > (or through the web based interface)
210 and disable this feature. If you use more than one browser, it would make
211 more sense to let <SPAN
214 > handle this. In which
215 case, the browser(s) should be set to accept all cookies.</P
217 > Another feature where you will probably want to define exceptions for trusted
218 sites is the popup-killing (through the <TT
225 > actions), because your favorite shopping,
226 banking, or leisure site may need popups (explained below). </P
231 > is HTTP/1.1 compliant, but not all of
232 the optional 1.1 features are as yet supported. In the unlikely event that
233 you experience inexplicable problems with browsers that use HTTP/1.1 per default
237 > or recent versions of I.E.), you might
238 try to force HTTP/1.0 compatibility. For Mozilla, look under <TT
241 Preferences -> Debug -> Networking</TT
243 Alternatively, set the <SPAN
245 >"+downgrade-http-version"</SPAN
250 > which will downgrade your browser's HTTP
251 requests from HTTP/1.1 to HTTP/1.0 before processing them.</P
253 > After running <SPAN
256 > for a while, you can
257 start to fine tune the configuration to suit your personal, or site,
258 preferences and requirements. There are many, many aspects that can
263 can be adjusted by pointing your browser to
265 HREF="http://config.privoxy.org/"
267 >http://config.privoxy.org/</A
274 and then follow the link to <SPAN
276 >"View & Change the Current Configuration"</SPAN
278 (This is an internal page and does not require Internet access.)</P
280 > In fact, various aspects of <SPAN
284 configuration can be viewed from this page, including
285 current configuration parameters, source code version numbers,
286 the browser's request headers, and <SPAN
290 to a given URL. In addition to the actions file
291 editor mentioned above, <SPAN
301 > (toggled) from this page.</P
303 > If you encounter problems, try loading the page without
307 >. If that helps, enter the URL where
308 you have the problems into <A
309 HREF="http://p.p/show-url-info"
312 based rule tracing utility</A
313 >. See which rules apply and why, and
314 then try turning them off for that site one after the other, until the problem
315 is gone. When you have found the culprit, you might want to turn the rest on
318 > If the above paragraph sounds gibberish to you, you might want to <A
319 HREF="configuration.html#ACTIONSFILE"
321 >read more about the actions concept</A
323 or even dive deep into the <A
324 HREF="appendix.html#ACTIONSANAT"
330 > If you can't get rid of the problem at all, think you've found a bug in
331 Privoxy, want to propose a new feature or smarter rules, please see the
347 >6.1. Command Line Options</A
353 > may be invoked with the following
354 command-line options:</P
367 > Print version info and exit. Unix only.
378 > Print short usage info and exit. Unix only.
389 > Don't become a daemon, i.e. don't fork and become process group
390 leader, and don't detach from controlling tty. Unix only.
402 > On startup, write the process ID to <I
409 > on exit. Failure to create or delete the
413 > is non-fatal. If no <I
417 option is given, no PID file will be used. Unix only.
424 >--user USER[.GROUP]</I
429 > After (optionally) writing the PID file, assume the user ID of
433 >, and if included the GID of GROUP. Exit if the
434 privileges are not sufficient to do so. Unix only.
448 > is included on the command line,
452 > will look for a file named
456 > in the current directory (except on Win32
457 where it will look for <SPAN
461 full path to avoid confusion. If no config file is found,
465 > will fail to start.
487 HREF="quickstart.html"
503 HREF="configuration.html"
512 >Quickstart to Using <SPAN