https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412007-08-15T11:05:49Zlighty labsLighttpd - Feature #1284: lighttpd don't print keep alive answering headerhttps://redmine.lighttpd.net/issues/1284?journal_id=31642007-08-15T11:05:49Zjan
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Assigned</i></li></ul><p>For HTTP/1.1</p>
<pre>
Connection: Keep-Alive
</pre>
<p>is the default and doesn't have to be specified.</p>
<p>The Keep-Alive header is not specified in the RFC 2616 and I wonder where it is documented.</p> Lighttpd - Feature #1284: lighttpd don't print keep alive answering headerhttps://redmine.lighttpd.net/issues/1284?journal_id=31652007-08-15T14:31:53Zjoungkyun
<ul></ul><p>Keep-Alive: header is optional. (<a class="external" href="http://tools.ietf.org/html/rfc2068">http://tools.ietf.org/html/rfc2068</a> 19.7.1.1)</p>
<p>But, sometimes some libraries (for example, libtorrent and so on..) check this header. So, I want to be support this function on lighttpd.</p> Lighttpd - Feature #1284: lighttpd don't print keep alive answering headerhttps://redmine.lighttpd.net/issues/1284?journal_id=31662008-07-30T21:45:51Zstbuehler
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Fixed</i></li><li><strong>Resolution</strong> set to <i>wontfix</i></li></ul><pre>
The Keep-Alive header itself is optional, and is used only if a
parameter is being sent. HTTP/1.1 does not define any parameters.
</pre>
<p>So there are no standard params, there is reason to use it.</p> Lighttpd - Feature #1284: lighttpd don't print keep alive answering headerhttps://redmine.lighttpd.net/issues/1284?journal_id=48352008-10-10T19:05:03Zstbuehler
<ul><li><strong>Status</strong> changed from <i>Fixed</i> to <i>Wontfix</i></li></ul>