diff options
author | Marco Bonetti <sid77@slackware.it> | 2010-05-12 23:32:41 +0200 |
---|---|---|
committer | David Somero <xgizzmo@slackbuilds.org> | 2010-05-12 23:32:41 +0200 |
commit | 54fed56da4e8d0f76e8cf9eac9ac54b09c6a6390 (patch) | |
tree | 055325f19c4cd9e1e55a51679331323ef17db713 /network/polipo/README | |
parent | 045310e29ea3fe6b68510d9a2a3b96b6588f7248 (diff) |
network/polipo: Added to 12.2 repository
Diffstat (limited to 'network/polipo/README')
-rw-r--r-- | network/polipo/README | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/network/polipo/README b/network/polipo/README new file mode 100644 index 000000000000..f9c4c2f41b6d --- /dev/null +++ b/network/polipo/README @@ -0,0 +1,23 @@ +Polipo is a small and fast caching web proxy (a web cache, an HTTP proxy, a +proxy server). While Polipo was designed to be used by one person or a small +group of people, there is nothing that prevents it from being used by a larger +group. + +Polipo has some features that are, as far as I know, unique among currently +available proxies: + * Polipo will use HTTP/1.1 pipelining if it believes that the remote server + supports it, whether the incoming requests are pipelined or come in + simultaneously on multiple connections (this is more than the simple usage + of persistent connections, which is done by e.g. Squid); Polipo will cache + the initial segment of an instance if the download has been interrupted, + and, if necessary, complete it later using Range requests; + * Polipo will upgrade client requests to HTTP/1.1 even if they come in as + HTTP/1.0, and up- or downgrade server replies to the client's capabilities + (this may involve conversion to or from the HTTP/1.1 chunked encoding); + * Polipo has complete support for IPv6 (except for scoped (link-local) + addresses). + * Polipo can optionally use a technique known as Poor Man's Multiplexing to + reduce latency even further. + +In short, Polipo uses a plethora of techniques to make web browsing (seem) +faster. |