/usr/share/polipo/www/doc/Server_002dside-behaviour.html is in polipo 1.0.4.1-1.2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 | <html lang="en">
<head>
<title>Server-side behaviour - The Polipo Manual</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="The Polipo Manual">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Network.html#Network" title="Network">
<link rel="prev" href="Server-statistics.html#Server-statistics" title="Server statistics">
<link rel="next" href="PMM.html#PMM" title="PMM">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 2003 -- 2006 by Juliusz Chroboczek.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Server-side-behaviour"></a>
<a name="Server_002dside-behaviour"></a>
<p>
Next: <a rel="next" accesskey="n" href="PMM.html#PMM">PMM</a>,
Previous: <a rel="previous" accesskey="p" href="Server-statistics.html#Server-statistics">Server statistics</a>,
Up: <a rel="up" accesskey="u" href="Network.html#Network">Network</a>
<hr>
</div>
<h3 class="section">3.6 Tweaking server-side behaviour</h3>
<p><a name="index-serverSlots-114"></a><a name="index-serverSlots1-115"></a><a name="index-serverMaxSlots-116"></a><a name="index-smallRequestTime-117"></a><a name="index-replyUnpipelineTime-118"></a><a name="index-replyUnpipelineSize-119"></a><a name="index-maxPipelineTrain-120"></a><a name="index-pipelineAdditionalRequests-121"></a><a name="index-maxSideBuffering-122"></a><a name="index-small-request-123"></a><a name="index-large-request-124"></a><a name="index-breaking-pipelines-125"></a>
The most important piece of information about a server is whether it
supports persistent connections. If this is the case, Polipo will
open at most <code>serverSlots</code> connections to that server
(<code>serverSlots1</code> if the server only implements HTTP/1.0), and
attempt to pipeline; if not, Polipo will hit the server harder,
opening up to <code>serverMaxSlots</code> connections.
<p>Another use of server information is to decide whether to pipeline
additional requests on a connection that already has in-flight
requests. This is controlled by the variable
<code>pipelineAdditionalRequests</code>; if it is <code>false</code>, no
additional requests will be pipelined. If it is <code>true</code>,
additional requests will be pipelined whenever possible. If it is
<code>maybe</code> (the default), additional requests will only be pipelined
following <dfn>small</dfn> requests, where a small request one whose
download is estimated to take no more than <code>smallRequestTime</code>
(default 5<span class="dmn">s</span>).
<p>Sometimes, a request has been pipelined after a request that prompts a
very large reply from the server; when that happens, the pipeline
needs be broken in order to reduce latency. A reply is <dfn>large</dfn>
and will cause a pipeline to be broken if either its size is at least
<code>replyUnpipelineSize</code> (default one megabyte) or else the server's
transfer rate is known and the body is expected to take at least
<code>replyUnpipelineTime</code> to download (default 15<span class="dmn">s</span>).
<p>The variable <code>maxPipelineTrain</code> defines the maximum number of
requests that will be pipelined in a single write (default 10).
Setting this variable to a very low value might (or might not) fix
interaction with some unreliable servers that the normal heuristics
are unable to detect.
<p>The variable <code>maxSideBuffering</code> specifies how much data will be
buffered in a PUT or POST request; it defaults to 1500 bytes. Setting
this variable to 0 may cause some media players that abuse the HTTP
protocol to work.
</body></html>
|