Any browser that can be configured to use a "proxy", which
- should be virtually all browsers. Direct browser support is not necessary
- since Any browser that can be configured to use a proxy, which
+ should be virtually all browsers, including
+ Firefox, Internet
+ Explorer, Opera, and
+ Safari among others.
+ Direct browser support is not an absolute requirement since
+ Privoxy runs as a separate application and
- just exchanges standard HTML data with your browser, just like a web server
+> runs as a separate application and talks
+ to the browser in the standardized HTTP protocol, just like a web server
does.
Privoxy is known to run on
- Windows(95, 98, ME, 2000, XP), Linux (RedHat, Suse, Debian), Mac OSX,
- OS/2, AmigaOS, FreeBSD, NetBSD, BeOS, and many more flavors of Unix.
But any operating system that runs TCP/IP, can conceivably take advantage of
"gateway" needs to be running one of the above
- operating systems.
Source code is freely available, so porting to other operating systems,
+> Source code is freely available, so porting to other operating systems
is always a possibility.
As long as there is some way to set a HTTP proxy for the client, then yes,
+ any application can be used, whether it is strictly speaking a
"browser" or not. Though this may not be the best approach for
+ dealing with some of the common abuses of HTML in email. See How can I configure Privoxy over
+ with JunkbusterOutlook? below for more on
+ this.
We recommend you uninstall Junkbuster
- first to minimize conflicts and confusion. You may want to
- save your old configuration files for future reference. The configuration
- is substantially changed.
-
See the user-manual for
- platform specific installation instructions.
-
Note: Some installers may automatically uninstall
- Junkbuster, if present!
-
Be aware that HTML email presents a number of unique security and privacy
+ related issues, that can require advanced skills to overcome. The developers
+ recommend using email clients that can be configured to convert HTML to plain
+ text for these reasons.
All browsers must be told to use All browsers should be told to use Privoxy
as a proxy by specifying the correct proxy address and port number
- in the appropriate configuration area for the browser. See below.
- Also, you should flush your browser's memory and disk cache to get rid of any
- cached items.
Privoxy with a packet filter to intercept HTTP requests
+ even if the client isn't explicitly configured to use Privoxy,
+ but where possible, configuring the client is recommended. See
+ the User Manual for more
+ details. You should also flush your browser's memory and disk
+ cache to get rid of any cached junk items, and remove any stored
+ cookies.
If you set up the Privoxy to run on
the computer you browse from (rather than your ISP's server or some
- networked computer on a LAN), the proxy will be on 127.0.0.1
+ (sometimes referred to as "localhost",
+ which is the special name used by every computer on the Internet to refer
+ to itself) and the port will be 8118 (unless you used the listen-address
- (which is the special name used by every computer on the Internet to refer
- to itself) and the port will be 8118 (unless you have Privoxy to run on a different port with the
- listen-address config option).
+> to run on
+ a different port).
When configuring your browser's proxy settings you typically enter
the word "localhost" in the boxes next to or the IP address "HTTP""127.0.0.1"
- and "HTTP" and "Secure" (HTTPS) and then the number (HTTPS) and
+ then the number "8118"
- for for "port". This tells your browser to send all web
- requests to .
+ This tells your browser to send all web requests to Privoxy instead of directly to the
- Internet.
+>
+ instead of directly to the Internet.
Privoxy
- is running, or the equivalent hostname. Port assignment would be
- same as above.
+ is running, or the equivalent hostname, e.g. 192.168.1.1.
+ Port assignment would be same as above. Note that
+ Privoxy doesn't listen on any LAN interfaces by
+ default.
Privoxy does not currently handle
- protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
- protocols.
+ any other protocols such as FTP, SMTP, IM, IRC, ICQ, etc.
http://p.p/. This should give you
- a banner that says .
+
+ This should take you to a page titled "This is Privoxy" and
+>"This is Privoxy.." with
access to Privoxy's internal configuration.
- If you see this, then you are good to go. If not, the browser or
+> internal configuration.
+ If you see this, then you are good to go. If you receive a page saying
"Privoxy is not running", then the browser is not set up to use
+ your Privoxy installation.
+ If you receive anything else (probably nothing at all), it could either
+ be that the browser is not set up correctly, or that
+ Privoxy is not running at all. Check the log file. For instructions
+ on starting Privoxy and browser configuration,
+ see the chapter
+ on starting Privoxy in the
+ User Manual.
Now if http://p.p/ works for you, but
+ other parts of Privoxy's web interface show
+ the dummy page, your browser has cached a redirection it encountered before
+ Privoxy was being used. You need to clear your
+ browser's cache. Note that shift-reloading the dummy page won't help, since
+ that'll only refresh the dummy page, not the redirection that lead you there.
The procedure for clearing the cache varies from browser to browser. For
+ example, Mozilla/Netscape users would click
+ Edit --> Preferences -->
+ Advanced --> Cache and
+ then click both "Clear Memory Cache"
+ and "Clear Disk Cache".
+ In some Firefox versions it's
+ Tools --> Options -->
+ Privacy --> Cache and
+ then click "Clear Cache Now".
+