4 >Quickstart to Using Privoxy</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy User Manual"
10 HREF="index.html"><LINK
13 HREF="installation.html"><LINK
15 TITLE="Privoxy Configuration"
16 HREF="configuration.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy User Manual</TH
46 HREF="installation.html"
59 HREF="configuration.html"
73 >4. Quickstart to Using <SPAN
79 > Before launching <SPAN
82 > for the first time, you
83 will want to configure your browser(s) to use <SPAN
87 as a HTTP and HTTPS proxy. The default is localhost for the proxy address,
88 and port 8118 (earlier versions used port 800). This is the one required
89 configuration that must be done! </P
99 >), this can be set under <TT
102 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</TT
106 >Internet Explorer</SPAN
110 Internet Properties -> Connections -> LAN Setting</TT
115 > and fill in the appropriate info (Address:
116 localhost, Port: 8118). Include if HTTPS proxy support too.</P
118 > After doing this, flush your browser's disk and memory caches to force a
119 re-reading of all pages and get rid of any ads that may be cached. You
120 are now ready to start enjoying the benefits of using
129 > is typically started by specifying the
130 main configuration file to be used on the command line. Example Unix startup
142 # /usr/sbin/privoxy /etc/privoxy/config
150 > An init script is provided for SuSE and Redhat.</P
154 >/etc/rc.d/privoxy start</B
159 >/etc/rc.d/init.d/privoxy start</B
162 > If no configuration file is specified on the command line,
166 > will look for a file named
170 > in the current directory. Except on Win32 where
174 >. If no file is specified on the
175 command line and no default configuration file can be found,
179 > will fail to start.</P
181 > The included default configuration files should give a reasonable starting
182 point, though may be somewhat aggressive in blocking junk. Most of the
183 per site configuration is done in the <SPAN
187 are where various cookie actions are defined, ad and banner blocking,
188 and other aspects of <SPAN
191 > configuration. There
192 are several such files included, with varying levels of aggressiveness. </P
194 > You will probably want to keep an eye out for sites that require persistent
195 cookies, and add these to <TT
199 default, most of these will be accepted only during the current browser
200 session, until you add them to the configuration. If you want the browser to
201 handle this instead, you will need to edit
205 > and disable this feature. If you use more
206 than one browser, it would make more sense to let
210 > handle this. In which case, the browser(s)
211 should be set to accept all cookies.</P
216 > is HTTP/1.1 compliant, but not all 1.1
217 features are as yet implemented. If browsers that support HTTP/1.1 (like
221 > or recent versions of I.E.) experience
222 problems, you might try to force HTTP/1.0 compatibility. For Mozilla, look
225 >Edit -> Preferences -> Debug -> Networking</TT
236 > After running <SPAN
239 > for a while, you can
240 start to fine tune the configuration to suit your personal, or site,
241 preferences and requirements. There are many, many aspects that can
245 > (as specified in <TT
249 can be adjusted by pointing your browser to
255 and then follow the link to <SPAN
257 >"edit the actions list"</SPAN
259 (This is an internal page and does not require Internet access.)</P
261 > In fact, various aspects of <SPAN
265 configuration can be viewed from this page, including
266 current configuration parameters, source code version numbers,
267 the browser's request headers, and <SPAN
271 to a given URL. In addition to the <TT
275 editor mentioned above, <SPAN
287 > If you encounter problems, please verify it is a
295 >, and then trying the same page.
296 Also, try another browser if possible to eliminate browser or site
297 problems. Before reporting it as a bug, see if there is not a configuration
298 option that is enabled that is causing the page not to load. You can then add
299 an exception for that page or site. For instance, try adding it to the
307 This will turn off most actions for this site. For more on troubleshooting
308 problem sites, see the <A
309 HREF="appendix.html#ACTIONSANAT"
312 >. If a bug, please report it
313 to the developers (see below). </P
320 >4.1. Command Line Options</A
326 > may be invoked with the following
327 command-line options:</P
340 > Print version info and exit, Unix only.
351 > Print a short usage info and exit, Unix only.
362 > Don't become a daemon, i.e. don't fork and become process group
363 leader, don't detach from controlling tty. Unix only.
375 > On startup, write the process ID to <I
382 > on exit. Failiure to create or delete the
386 > is non-fatal. If no <I
390 option is given, no PID file will be used. Unix only.
397 >--user USER[.GROUP]</I
402 > After (optionally) writing the PID file, assume the user ID of
406 >, and if included the GID of GROUP. Exit if the
407 privileges are not sufficient to do so. Unix only.
421 > is included on the command line,
425 > will look for a file named
429 > in the current directory (except on Win32
430 where it will look for <SPAN
434 full path to avoid confusion.
456 HREF="installation.html"
472 HREF="configuration.html"