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
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 800). This is the one required
90 configuration 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 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
151 > An init script is provided for SuSE and Redhat.</P
155 >/etc/rc.d/privoxy start</B
160 >/etc/rc.d/init.d/privoxy start</B
163 > If no configuration file is specified on the command line,
167 > will look for a file named
171 > in the current directory. Except on Win32 where
175 >. If no file is specified on the
176 command line and no default configuration file can be found,
180 > will fail to start.</P
182 > The included default configuration files should give a reasonable starting
183 point, though may be somewhat aggressive in blocking junk. Most of the
184 per site configuration is done in the <SPAN
188 are where various cookie actions are defined, ad and banner blocking,
189 and other aspects of <SPAN
192 > configuration. There
193 are several such files included, with varying levels of aggressiveness. </P
195 > You will probably want to keep an eye out for sites that require persistent
196 cookies, and add these to <TT
200 default, most of these will be accepted only during the current browser
201 session, until you add them to the configuration. If you want the browser to
202 handle this instead, you will need to edit
206 > and disable this feature. If you use more
207 than one browser, it would make more sense to let
211 > handle this. In which case, the browser(s)
212 should be set to accept all cookies.</P
217 > is HTTP/1.1 compliant, but not all 1.1
218 features are as yet implemented. If browsers that support HTTP/1.1 (like
222 > or recent versions of I.E.) experience
223 problems, you might try to force HTTP/1.0 compatibility. For Mozilla, look
226 >Edit -> Preferences -> Debug -> Networking</TT
237 > After running <SPAN
240 > for a while, you can
241 start to fine tune the configuration to suit your personal, or site,
242 preferences and requirements. There are many, many aspects that can
246 > (as specified in <TT
250 can be adjusted by pointing your browser to
256 and then follow the link to <SPAN
258 >"edit the actions list"</SPAN
260 (This is an internal page and does not require Internet access.)</P
262 > In fact, various aspects of <SPAN
266 configuration can be viewed from this page, including
267 current configuration parameters, source code version numbers,
268 the browser's request headers, and <SPAN
272 to a given URL. In addition to the <TT
276 editor mentioned above, <SPAN
288 > If you encounter problems, please verify it is a
296 >, and then trying the same page.
297 Also, try another browser if possible to eliminate browser or site
298 problems. Before reporting it as a bug, see if there is not a configuration
299 option that is enabled that is causing the page not to load. You can then add
300 an exception for that page or site. For instance, try adding it to the
308 This will turn off most actions for this site. For more on troubleshooting
309 problem sites, see the <A
310 HREF="appendix.html#ACTIONSANAT"
313 >. If a bug, please report it
314 to the developers (see below). </P
321 >4.1. Command Line Options</A
327 > may be invoked with the following
328 command-line options:</P
341 > Print version info and exit, Unix only.
352 > Print a short usage info and exit, Unix only.
363 > Don't become a daemon, i.e. don't fork and become process group
364 leader, don't detach from controlling tty. Unix only.
376 > On startup, write the process ID to <I
383 > on exit. Failiure to create or delete the
387 > is non-fatal. If no <I
391 option is given, no PID file will be used. Unix only.
398 >--user USER[.GROUP]</I
403 > After (optionally) writing the PID file, assume the user ID of
407 >, and if included the GID of GROUP. Exit if the
408 privileges are not sufficient to do so. Unix only.
422 > is included on the command line,
426 > will look for a file named
430 > in the current directory (except on Win32
431 where it will look for <SPAN
435 full path to avoid confusion.
457 HREF="installation.html"
473 HREF="configuration.html"