1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Starting Privoxy</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy 3.0.7 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
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.7 User Manual</TH
50 HREF="quickstart.html"
64 HREF="configuration.html"
79 >5. Starting Privoxy</A
82 > Before launching <SPAN
85 > for the first time, you
86 will want to configure your browser(s) to use
90 > as a HTTP and HTTPS (SSL)
92 HREF="http://en.wikipedia.org/wiki/Proxy_server"
96 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
97 used port 8000). This is the one configuration step <SPAN
101 >that must be done</I
105 > Please note that <SPAN
108 > can only proxy HTTP and
109 HTTPS traffic. It will not work with FTP or other protocols.</P
118 >Figure 2. Proxy Configuration Showing
119 Mozilla/Netscape HTTP and HTTPS (SSL) Settings</B
125 SRC="proxy_setup.jpg"></P
135 >, this is typically set under:</P
137 CLASS="LITERALLAYOUT"
141 > -> <SPAN
144 > -> <SPAN
147 > -> <SPAN
149 >Connection Settings</SPAN
150 > -> <SPAN
152 >Manual Proxy Configuration</SPAN
156 Or optionally on some platforms:</P
158 CLASS="LITERALLAYOUT"
162 > -> <SPAN
165 > -> <SPAN
168 > -> <SPAN
170 >Connection Settings</SPAN
171 > -> <SPAN
173 >Manual Proxy Configuration</SPAN
184 >), this can be set under:</P
186 CLASS="LITERALLAYOUT"
190 > -> <SPAN
193 > -> <SPAN
196 > -> <SPAN
199 > -> <SPAN
206 >Internet Explorer v.5-6</SPAN
209 CLASS="LITERALLAYOUT"
213 > -> <SPAN
215 >Internet Options</SPAN
216 > -> <SPAN
219 > -> <SPAN
227 > and fill in the appropriate info
228 (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
229 proxy support too (sometimes labeled <SPAN
233 checkboxes like <SPAN
235 >"Use the same proxy server for all protocols"</SPAN
243 >. You want only HTTP and HTTPS (SSL)!</P
252 >Figure 3. Proxy Configuration Showing
253 Internet Explorer HTTP and HTTPS (Secure) Settings</B
265 > After doing this, flush your browser's disk and memory caches to force a
266 re-reading of all pages and to get rid of any ads that may be cached. Remove
268 HREF="http://en.wikipedia.org/wiki/Browser_cookie"
275 > to manage that. You are now
276 ready to start enjoying the benefits of using
285 > itself is typically started by specifying the
286 main configuration file to be used on the command line. If no configuration
287 file is specified on the command line, <SPAN
291 will look for a file named <TT
295 directory. Except on Win32 where it will try <TT
305 >5.1. Red Hat and Fedora</A
308 > A default Red Hat installation may not start <SPAN
311 > upon boot. It will use
314 >/etc/privoxy/config</TT
315 > as its main configuration
326 > # /etc/rc.d/init.d/privoxy start</PRE
342 > # service privoxy start</PRE
357 > We use a script. Note that Debian typically starts <SPAN
361 default. It will use the file
364 >/etc/privoxy/config</TT
365 > as its main configuration
376 > # /etc/init.d/privoxy start</PRE
394 > Icon to start <SPAN
397 >. If no configuration file is
398 specified on the command line, <SPAN
405 >. Note that Windows will
406 automatically start <SPAN
409 > when the system starts if you chose that option
415 > can run with full Windows service functionality.
416 On Windows only, the <SPAN
419 > program has two new command line arguments
420 to install and uninstall <SPAN
423 > as a service. See the
425 HREF="installation.html#INSTALLATION-PACK-WIN"
426 >Windows Installation
436 >5.4. Solaris, NetBSD, FreeBSD, HP-UX and others</A
439 >Example Unix startup command:</P
449 > # /usr/sbin/privoxy /etc/privoxy/config</PRE
464 > During installation, <SPAN
468 start automatically when the system restarts. You can start it manually by
469 double-clicking on the <SPAN
487 > During installation, <SPAN
491 start automatically when the system restarts. To start <SPAN
495 double-click on the <TT
497 >StartPrivoxy.command</TT
501 >/Library/Privoxy</TT
502 > folder. Or, type this command
513 > /Library/Privoxy/StartPrivoxy.command
520 > You will be prompted for the administrator password.</P
534 > (with RUN <>NIL:) in your
538 > script (AmiTCP), in
542 > (RoadShow), as startup program in your
543 startup script (Genesis), or as startup action (Miami and MiamiDx).
547 > will automatically quit when you quit your
548 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
552 > is still running).</P
563 > A script is again used. It will use the file <TT
567 > as its main configuration file.</P
577 > /etc/init.d/privoxy start
587 > is not automatically started at
588 boot time by default. You can change this with the <TT
603 > rc-update add privoxy default
616 >5.9. Command Line Options</A
622 > may be invoked with the following
623 command-line options:</P
639 > Print version info and exit. Unix only.
653 > Print short usage info and exit. Unix only.
667 > Don't become a daemon, i.e. don't fork and become process group
668 leader, and don't detach from controlling tty. Unix only.
682 > On startup, write the process ID to <SPAN
695 > on exit. Failure to create or delete the
702 > is non-fatal. If no <SPAN
709 option is given, no PID file will be used. Unix only.
718 >--user USER[.GROUP]</I
723 > After (optionally) writing the PID file, assume the user ID of
730 >, and if included the GID of GROUP. Exit if the
731 privileges are not sufficient to do so. Unix only.
745 > Before changing to the user ID given in the <SPAN
752 chroot to that user's home directory, i.e. make the kernel pretend to the <SPAN
756 process that the directory tree starts there. If set up carefully, this can limit
757 the impact of possible vulnerabilities in <SPAN
760 > to the files contained in that hierarchy.
770 >--pre-chroot-nslookup hostname</I
775 > Specifies a hostname to look up before doing a chroot. On some systems, initializing the
776 resolver library involves reading config files from /etc and/or loading additional shared
777 libraries from /lib. On these systems, doing a hostname lookup before the chroot reduces
778 the number of files that must be copied into the chroot tree.
781 > For fastest startup speed, a good value is a hostname that is not in /etc/hosts but that
782 your local name server (listed in /etc/resolv.conf) can resolve without recursion
783 (that is, without having to ask any other name servers). The hostname need not exist,
784 but if it doesn't, an error message (which can be ignored) will be output.
804 > is included on the command line,
808 > will look for a file named
812 > in the current directory (except on Win32
813 where it will look for <SPAN
817 full path to avoid confusion. If no config file is found,
821 > will fail to start.
830 > only there are two additional
831 command-line options to allow <SPAN
843 HREF="installation.html#INSTALLATION-PACK-WIN"
844 >Window Installation section</A
854 SUMMARY="Footer navigation table"
865 HREF="quickstart.html"
883 HREF="configuration.html"
893 >Quickstart to Using Privoxy</TD
903 >Privoxy Configuration</TD