Privoxy Privoxy is a web proxy with advanced filtering capabilities for protecting privacy.
Download

Privoxy Ranking & Summary

Privoxy Tags

web proxy web proxy Privoxy protecting privacy managing cookies

Privoxy Description

Privoxy is a web proxy with advanced filtering capabilities for protecting privacy. Privoxy is a web proxy with advanced filtering capabilities for protecting privacy, modifying web page content, managing cookies, controlling access, and removing ads, banners, pop-ups and other obnoxious Internet junk.Privoxy has a very flexible configuration and can be customized to suit individual needs and tastes. Privoxy has application for both stand-alone systems and multi-user networks.Privoxy is based on Internet Junkbuster. Here are some key features of "Privoxy": · Integrated browser based configuration and control utility at http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based tracing of rule and filter effects. Remote toggling. · Web page content filtering (removes banners based on size, invisible "web-bugs", JavaScript and HTML annoyances, pop-up windows, etc.) · Modularized configuration that allows for standard settings and user settings to reside in separate files, so that installing updated actions files won't overwrite individual user settings. · HTTP/1.1 compliant (but not all optional 1.1 features are supported). · Support for Perl Compatible Regular Expressions in the configuration files, and generally a more sophisticated and flexible configuration syntax over previous versions. · Improved cookie management features (e.g. session based cookies). · GIF de-animation. · Bypass many click-tracking scripts (avoids script redirection). · Multi-threaded (POSIX and native threads). · User-customizable HTML templates for all proxy-generated pages (e.g. "blocked" page). · Auto-detection and re-reading of config file changes. · Improved signal handling, and a true daemon mode (Unix). · Every feature now controllable on a per-site or per-location basis, configuration more powerful and versatile over-all. · Many smaller new features added, limitations and bugs removed, and security holes fixed. What's New in This Release: · Added IPv6 support. Thanks to Petr Pisar who not only provided the initial patch but also helped a lot with the integration. · Added client-side keep-alive support. This should also allow NTLM authentication through Privoxy, but this hasn't been confirmed yet. · The connection sharing code is only used if the connection-sharing option is enabled. · The max-client-connections option has been added to restrict the number of client connections below a value enforced by the operating system. · Fixed a regression reintroduced in 3.0.12 that could cause crashes on mingw32 if header date randomization was enabled. · Compressed content with extra fields couldn't be decompressed and would get passed to the client unfiltered. This problem has only be detected through statical analysis with clang as nobody seems to be using extra fields anyway. · If the server resets the Connection after sending only the headers Privoxy forwards what it got to the client. Previously Privoxy would deliver an error message instead. · Error messages in case of connection timeouts use the right HTTP status code. · If spawning a child to handle a request fails, the client gets an error message and Privoxy continues to listen for new requests right away. · The error messages in case of server-connection timeouts or prematurely closed server connections are now template-based. · If zlib support isn't compiled in, Privoxy no longer tries to filter compressed content unless explicitly asked to do so. · In case of connections that are denied based on ACL directives, the memory used for the client IP is no longer leaked. · Fixed another small memory leak if the client request times out while waiting for client headers other than the request line. · The client socket is kept open until the server socket has been marked as unused. This should increase the chances that the still-open connection will be reused for the client's next request to the same destination. Note that this only matters if connection-sharing is enabled. · A TODO list has been added to the source tarballs to give potential volunteers a better idea of what the current goals are. Donations are still welcome too: http://www.privoxy.org/faq/general.html#DONATE

Privoxy Related Software