1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Starting Privoxy</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="Privoxy 3.0.3 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
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.3 User Manual</TH
48 HREF="quickstart.html"
62 HREF="configuration.html"
83 > Before launching <SPAN
86 > for the first time, you
87 will want to configure your browser(s) to use
91 > as a HTTP and HTTPS proxy. The default is
92 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
93 used port 8000). This is the one configuration step that must be done!</P
95 > Please note that <SPAN
98 > can only proxy HTTP and
99 HTTPS traffic. It will not work with FTP or other protocols.</P
108 >Figure 2. Proxy Configuration (Mozilla)</B
114 SRC="../images/proxy_setup.jpg"></P
128 >), this can be set under:</P
130 CLASS="LITERALLAYOUT"
135 |_ <br>
136 <SPAN
140 |_ <br>
141 <SPAN
145 |_ <br>
146 <SPAN
150 |_ <br>
151 <SPAN
158 >Internet Explorer</SPAN
161 CLASS="LITERALLAYOUT"
166 |_ <br>
167 <SPAN
169 >Internet Properties</SPAN
171 |_ <br>
172 <SPAN
176 |_ <br>
177 <SPAN
185 > and fill in the appropriate info
186 (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
187 proxy support too. </P
189 > After doing this, flush your browser's disk and memory caches to force a
190 re-reading of all pages and to get rid of any ads that may be cached. You
191 are now ready to start enjoying the benefits of using
200 > is typically started by specifying the
201 main configuration file to be used on the command line. If no configuration
202 file is specified on the command line, <SPAN
206 will look for a file named <TT
210 directory. Except on Win32 where it will try <TT
220 >5.1. Red Hat and Conectiva</A
223 > We use a script. Note that Red Hat does not start Privoxy upon booting per
224 default. It will use the file <TT
226 >/etc/privoxy/config</TT
228 its main configuration file.</P
238 > # /etc/rc.d/init.d/privoxy start</PRE
253 > We use a script. Note that Debian starts Privoxy upon booting per
254 default. It will use the file
257 >/etc/privoxy/config</TT
258 > as its main configuration
269 > # /etc/init.d/privoxy start</PRE
284 >We use a script. It will use the file <TT
286 >/etc/privoxy/config</TT
288 as its main configuration file. Note that SuSE starts Privoxy upon booting
299 > # rcprivoxy start</PRE
314 >Click on the Privoxy Icon to start Privoxy. If no configuration file is
315 specified on the command line, <SPAN
322 >. Note that Windows will
323 automatically start Privoxy upon booting you PC.</P
331 >5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</A
334 >Example Unix startup command:</P
344 > # /usr/sbin/privoxy /etc/privoxy/config</PRE
359 > During installation, <SPAN
363 start automatically when the system restarts. You can start it manually by
364 double-clicking on the <SPAN
382 > During installation, <SPAN
386 start automatically when the system restarts. To start Privoxy by hand,
387 double-click on the <VAR
389 >StartPrivoxy.command</VAR
393 >/Library/Privoxy</VAR
394 > folder. Or, type this command
405 > /Library/Privoxy/StartPrivoxy.command
412 > You will be prompted for the administrator password.</P
426 > (with RUN <>NIL:) in your
430 > script (AmiTCP), in
434 > (RoadShow), as startup program in your
435 startup script (Genesis), or as startup action (Miami and MiamiDx).
439 > will automatically quit when you quit your
440 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
444 > is still running).</P
455 > A script is again used. It will use the file <TT
459 > as its main configuration file.</P
469 > /etc/init.d/privoxy start
479 > is not automatically started at
480 boot time by default. You can change this with the <VAR
495 > rc-update add privoxy default
508 >5.10. Command Line Options</A
514 > may be invoked with the following
515 command-line options:</P
531 > Print version info and exit. Unix only.
545 > Print short usage info and exit. Unix only.
559 > Don't become a daemon, i.e. don't fork and become process group
560 leader, and don't detach from controlling tty. Unix only.
575 > On startup, write the process ID to <SPAN
588 > on exit. Failure to create or delete the
595 > is non-fatal. If no <SPAN
602 option is given, no PID file will be used. Unix only.
611 >--user USER[.GROUP]</I
617 > After (optionally) writing the PID file, assume the user ID of
624 >, and if included the GID of GROUP. Exit if the
625 privileges are not sufficient to do so. Unix only.
640 > Before changing to the user ID given in the <SPAN
647 chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy
648 process that the directory tree starts there. If set up carefully, this can limit
649 the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy.
670 > is included on the command line,
674 > will look for a file named
678 > in the current directory (except on Win32
679 where it will look for <SPAN
683 full path to avoid confusion. If no config file is found,
687 > will fail to start.
699 SUMMARY="Footer navigation table"
710 HREF="quickstart.html"
728 HREF="configuration.html"
738 >Quickstart to Using <SPAN