->. If no file is specified on the
- command line and no default configuration file can be found,
- <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
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> configuration. There are several such
- files included, with varying levels of aggressiveness. </P
-><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
-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
-CLASS="LITERAL"
->+popup</TT
-> and
- <TT
-CLASS="LITERAL"
->+filter{popups}</TT
-> actions), because your favorite shopping,
- banking, or leisure site may need popups (explained below). </P
-><P
-> <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
- <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