>Starting Privoxy</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy User Manual"
+TITLE="Privoxy 3.0.4 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><DIV
CLASS="NAVHEADER"
><TABLE
+SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy User Manual</TH
+>Privoxy 3.0.4 User Manual</TH
></TR
><TR
><TD
VALIGN="bottom"
><A
HREF="quickstart.html"
+ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="bottom"
><A
HREF="configuration.html"
+ACCESSKEY="N"
>Next</A
></TD
></TR
CLASS="SECT1"
><A
NAME="STARTUP"
->6. Starting <SPAN
+></A
+>5. Starting <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-></A
></H1
><P
> Before launching <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> for the first time, you
- will want to configure your browser(s) to use <SPAN
+> for the first time, you
+ will want to configure your browser(s) to use
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> as a HTTP and HTTPS proxy. The default is
+ 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
+ used port 8000). This is the one configuration step that must be done!</P
+><P
+> Please note that <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
+> can only proxy HTTP and
+ HTTPS traffic. It will not work with FTP or other protocols.</P
+><P
+> <DIV
+CLASS="FIGURE"
+><A
+NAME="AEN558"
+></A
+><P
+><B
+>Figure 2. Proxy Configuration (Mozilla)</B
+></P
+><DIV
+CLASS="MEDIAOBJECT"
+><P
+><IMG
+SRC="../images/proxy_setup.jpg"></P
+></DIV
+></DIV
>
- as a HTTP and HTTPS proxy. The default is localhost for the proxy address,
- and port 8118 (earlier versions used port 8000). This is the one
- configuration step that must be done! </P
+ </P
+><P
+>
+ With <SPAN
+CLASS="APPLICATION"
+>Firefox</SPAN
+>, this can be set under:</P
+><P
+CLASS="LITERALLAYOUT"
+> <SPAN
+CLASS="GUIBUTTON"
+>Tools</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Options</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>General</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Connection Settings</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Manual Proxy Configuration</SPAN
+></P
><P
>
With <SPAN
<SPAN
CLASS="APPLICATION"
>Mozilla</SPAN
->), this can be set under <TT
-CLASS="LITERAL"
->Edit
- -> Preferences -> Advanced -> Proxies -> HTTP Proxy</TT
->.
- For <SPAN
+>), this can be set under:</P
+><P
+CLASS="LITERALLAYOUT"
+> <SPAN
+CLASS="GUIBUTTON"
+>Edit</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Preferences</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Advanced</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Proxies</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>HTTP Proxy</SPAN
+></P
+><P
+> For <SPAN
CLASS="APPLICATION"
>Internet Explorer</SPAN
->: <TT
-CLASS="LITERAL"
->Tools ->
- Internet Properties -> Connections -> LAN Setting</TT
->. Then,
- check <SPAN
+>: </P
+><P
+CLASS="LITERALLAYOUT"
+> <SPAN
+CLASS="GUIBUTTON"
+>Tools</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Internet Properties</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>Connections</SPAN
+><br>
+ |_ <br>
+ <SPAN
+CLASS="GUIBUTTON"
+>LAN Settings</SPAN
+></P
+><P
+> Then, check <SPAN
CLASS="QUOTE"
>"Use Proxy"</SPAN
-> and fill in the appropriate info (Address:
- localhost, Port: 8118). Include if HTTPS proxy support too.</P
+> and fill in the appropriate info
+ (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
+ proxy support too. </P
><P
> After doing this, flush your browser's disk and memory caches to force a
re-reading of all pages and to get rid of any ads that may be cached. You
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is typically started by specifying the
- main configuration file to be used on the command line. Example Unix startup
- command:</P
+> itself is typically started by specifying the
+ main configuration file to be used on the command line. If no configuration
+ file is specified on the command line, <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ will look for a file named <TT
+CLASS="FILENAME"
+>config</TT
+> in the current
+ directory. Except on Win32 where it will try <TT
+CLASS="FILENAME"
+>config.txt</TT
+>.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-REDHAT"
+></A
+>5.1. Red Hat and Conectiva</H2
+><P
+> We use a script. Note that Red Hat does not start Privoxy upon booting per
+ default. It will use the file <TT
+CLASS="FILENAME"
+>/etc/privoxy/config</TT
+> as
+ its main configuration file.</P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
->
- # /usr/sbin/privoxy /etc/privoxy/config</PRE
+> # /etc/rc.d/init.d/privoxy start</PRE
></TD
></TR
></TABLE
></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-DEBIAN"
+></A
+>5.2. Debian</H2
><P
-> See <A
-HREF="startup.html#CMDOPTIONS"
->below</A
-> for other command line options.</P
-><P
-> An init script is provided for SuSE and Red Hat.</P
+> We use a script. Note that Debian starts Privoxy upon booting per
+ default. It will use the file
+ <TT
+CLASS="FILENAME"
+>/etc/privoxy/config</TT
+> as its main configuration
+ file.</P
><P
-> For for SuSE: <B
-CLASS="COMMAND"
->rcprivoxy start</B
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> # /etc/init.d/privoxy start</PRE
+></TD
+></TR
+></TABLE
></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-SUSE"
+></A
+>5.3. SuSE</H2
+><P
+>We use a script. It will use the file <TT
+CLASS="FILENAME"
+>/etc/privoxy/config</TT
+>
+as its main configuration file. Note that SuSE starts Privoxy upon booting
+your PC.</P
><P
-> For Red Hat and Debian: <B
-CLASS="COMMAND"
->/etc/rc.d/init.d/privoxy start</B
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> # rcprivoxy start</PRE
+></TD
+></TR
+></TABLE
></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-WINDOWS"
+></A
+>5.4. Windows</H2
><P
-> If no configuration file is specified on the command line,
- <SPAN
+>Click on the Privoxy Icon to start Privoxy. If no configuration file is
+ specified on the command line, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> will look for a file named
- <TT
-CLASS="FILENAME"
->config</TT
-> in the current directory. Except on Win32 where
- it will try <TT
+> will look
+ for a file named <TT
CLASS="FILENAME"
>config.txt</TT
->. If no file is specified on the
- command line and no default configuration file can be found,
- <SPAN
+>. Note that Windows will
+ automatically start Privoxy upon booting you PC.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-UNICES"
+></A
+>5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</H2
+><P
+>Example Unix startup command:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> # /usr/sbin/privoxy /etc/privoxy/config</PRE
+></TD
+></TR
+></TABLE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-OS2"
+></A
+>5.6. OS/2</H2
+><P
+> During installation, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> will fail to start.</P
-><P
-> The included default configuration files should give a reasonable starting
- point. Most of the per site configuration is done in the
- <SPAN
-CLASS="QUOTE"
->"actions"</SPAN
-> files. These are where various cookie actions are
- defined, ad and banner blocking, and other aspects of
+> is configured to
+ start automatically when the system restarts. You can start it manually by
+ double-clicking on the <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> icon in the
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> configuration. There are several such
- files included, with varying levels of aggressiveness. </P
+> folder.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-MACOSX"
+></A
+>5.7. Mac OSX</H2
><P
-> You will probably want to keep an eye out for sites for which you may prefer
- persistent cookies, and add these to your actions configuration as needed. By
- default, most of these will be accepted only during the current browser
- session (aka <SPAN
-CLASS="QUOTE"
->"session cookies"</SPAN
->), unless you add them to the
- configuration. If you want the browser to handle this instead, you will need
- to edit <TT
-CLASS="FILENAME"
->user.action</TT
-> (or through the web based interface)
- and disable this feature. If you use more than one browser, it would make
- more sense to let <SPAN
+> During installation, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> handle this. In which
- case, the browser(s) should be set to accept all cookies.</P
-><P
-> Another feature where you will probably want to define exceptions for trusted
- sites is the popup-killing (through the <TT
+> is configured to
+ start automatically when the system restarts. To start Privoxy by hand,
+ double-click on the <TT
CLASS="LITERAL"
->+popup</TT
-> and
+>StartPrivoxy.command</TT
+> icon in the
<TT
CLASS="LITERAL"
->+filter{popups}</TT
-> actions), because your favorite shopping,
- banking, or leisure site may need popups (explained below). </P
+>/Library/Privoxy</TT
+> folder. Or, type this command
+ in the Terminal:</P
><P
-> <SPAN
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> /Library/Privoxy/StartPrivoxy.command
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> You will be prompted for the administrator password.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-AMIGAOS"
+></A
+>5.8. AmigaOS</H2
+><P
+> Start <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is HTTP/1.1 compliant, but not all of
- the optional 1.1 features are as yet supported. In the unlikely event that
- you experience inexplicable problems with browsers that use HTTP/1.1 per default
- (like <SPAN
-CLASS="APPLICATION"
->Mozilla</SPAN
-> or recent versions of I.E.), you might
- try to force HTTP/1.0 compatibility. For Mozilla, look under <TT
-CLASS="LITERAL"
->Edit ->
- Preferences -> Debug -> Networking</TT
->.
- Alternatively, set the <SPAN
-CLASS="QUOTE"
->"+downgrade-http-version"</SPAN
-> config option in
+> (with RUN <>NIL:) in your
<TT
CLASS="FILENAME"
->default.action</TT
-> which will downgrade your browser's HTTP
- requests from HTTP/1.1 to HTTP/1.0 before processing them.</P
-><P
-> After running <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> for a while, you can
- start to fine tune the configuration to suit your personal, or site,
- preferences and requirements. There are many, many aspects that can
- be customized. <SPAN
-CLASS="QUOTE"
->"Actions"</SPAN
->
- can be adjusted by pointing your browser to
- <A
-HREF="http://config.privoxy.org/"
-TARGET="_top"
->http://config.privoxy.org/</A
->
- (shortcut: <A
-HREF="http://p.p/"
-TARGET="_top"
->http://p.p/</A
->),
- and then follow the link to <SPAN
-CLASS="QUOTE"
->"View & Change the Current Configuration"</SPAN
->.
- (This is an internal page and does not require Internet access.)</P
-><P
-> In fact, various aspects of <SPAN
+>startnet</TT
+> script (AmiTCP), in
+ <TT
+CLASS="FILENAME"
+>s:user-startup</TT
+> (RoadShow), as startup program in your
+ startup script (Genesis), or as startup action (Miami and MiamiDx).
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
- configuration can be viewed from this page, including
- current configuration parameters, source code version numbers,
- the browser's request headers, and <SPAN
-CLASS="QUOTE"
->"actions"</SPAN
-> that apply
- to a given URL. In addition to the actions file
- editor mentioned above, <SPAN
+> will automatically quit when you quit your
+ TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> can also
- be turned <SPAN
-CLASS="QUOTE"
->"on"</SPAN
-> and <SPAN
-CLASS="QUOTE"
->"off"</SPAN
-> (toggled) from this page.</P
+> is still running).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="START-GENTOO"
+></A
+>5.9. Gentoo</H2
><P
-> If you encounter problems, try loading the page without
- <SPAN
+> A script is again used. It will use the file <TT
+CLASS="FILENAME"
+>/etc/privoxy/config
+ </TT
+> as its main configuration file.</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> /etc/init.d/privoxy start
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> Note that <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->. If that helps, enter the URL where
- you have the problems into <A
-HREF="http://p.p/show-url-info"
-TARGET="_top"
->the browser
- based rule tracing utility</A
->. See which rules apply and why, and
- then try turning them off for that site one after the other, until the problem
- is gone. When you have found the culprit, you might want to turn the rest on
- again.</P
-><P
-> If the above paragraph sounds gibberish to you, you might want to <A
-HREF="configuration.html#ACTIONSFILE"
-TARGET="_top"
->read more about the actions concept</A
->
- or even dive deep into the <A
-HREF="appendix.html#ACTIONSANAT"
-TARGET="_top"
->Appendix
- on actions</A
->.</P
+> is not automatically started at
+ boot time by default. You can change this with the <TT
+CLASS="LITERAL"
+>rc-update</TT
+>
+ command.</P
><P
-> If you can't get rid of the problem at all, think you've found a bug in
- Privoxy, want to propose a new feature or smarter rules, please see the
- section <A
-HREF="contact.html"
-TARGET="_top"
-><SPAN
-CLASS="QUOTE"
->"Contacting the
- Developers"</SPAN
-></A
-> below. </P
+>
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> rc-update add privoxy default
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="CMDOPTIONS"
->6.1. Command Line Options</A
-></H2
+></A
+>5.10. Command Line Options</H2
><P
> <SPAN
CLASS="APPLICATION"
><UL
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>--version</I
+></SPAN
>
</P
><P
></LI
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>--help</I
+></SPAN
>
</P
><P
></LI
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>--no-daemon</I
+></SPAN
>
</P
><P
></LI
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>--pidfile FILE</I
+></SPAN
>
</P
><P
-> On startup, write the process ID to <I
+> On startup, write the process ID to <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>FILE</I
+></SPAN
>. Delete the
- <I
+ <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>FILE</I
+></SPAN
> on exit. Failure to create or delete the
- <I
+ <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>FILE</I
-> is non-fatal. If no <I
+></SPAN
+> is non-fatal. If no <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>FILE</I
+></SPAN
>
option is given, no PID file will be used. Unix only.
</P
></LI
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>--user USER[.GROUP]</I
+></SPAN
>
</P
><P
> After (optionally) writing the PID file, assume the user ID of
- <I
+ <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>USER</I
+></SPAN
>, and if included the GID of GROUP. Exit if the
privileges are not sufficient to do so. Unix only.
</P
></LI
><LI
><P
-> <I
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>--chroot</I
+></SPAN
+>
+
+ </P
+><P
+> Before changing to the user ID given in the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>--user</I
+></SPAN
+> option,
+ chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy
+ process that the directory tree starts there. If set up carefully, this can limit
+ the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy.
+ Unix only.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>configfile</I
+></SPAN
>
</P
><P
-> If no <I
+> If no <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>configfile</I
+></SPAN
> is included on the command line,
<SPAN
CLASS="APPLICATION"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
VALIGN="top"
><A
HREF="quickstart.html"
+ACCESSKEY="P"
>Prev</A
></TD
><TD
VALIGN="top"
><A
HREF="index.html"
+ACCESSKEY="H"
>Home</A
></TD
><TD
VALIGN="top"
><A
HREF="configuration.html"
+ACCESSKEY="N"
>Next</A
></TD
></TR
projects / privoxy.git / blobdiff