[web-devel] Connection: handling on Warp

Michael Snoyman michael at snoyman.com
Tue Jul 19 11:28:07 CEST 2011

On Tue, Jul 19, 2011 at 12:10 PM, Kazu Yamamoto <kazu at iij.ad.jp> wrote:
> Hello,
> Current Warp does not handle the Connection: header.
> For HTTP 1.1, RFC says that the connection is closed by an HTTP server
> if Connection: is "close" and it is not closed otherwise.
> For HTTP 1.0, RFC says that the connection is not closed if
> Connection: is "keep-alive" and it is closed otherwise.
> Current warp does not close connection, for example, for ResponseFile
> even if Connection: is not specified in HTTP 1.0.
> ab (ApacheBench) tries to create HTTP 1.0 connections and expects that
> the connections are closed by the server side. So, trying to benchmark
> Warp with "ab" results in getting stacked.
> I would like to add a proper handling of Connection: to Warp. What do
> you guys think?

This sounds good to me. Only reason I can think of to avoid it is the
extra bandwidth used by the header, but that's not really a good
reason not to use standards. Are you planning on writing a patch for


More information about the web-devel mailing list