Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Fri, 21 Sep 2001 16:49:01 -0700
From: "Roy T. Fielding" <fielding@ebuilt.com>
To: Ryan Bloom <rbb@covalent.net>
Cc: dev@httpd.apache.org
Subject: Re: New post-log-transaction hook?
Message-ID: <20010921164901.I1641@waka.ebuilt.net>
References: <20010917155221.A15053@covalent.net>
 <20010917163233.A15281@covalent.net>
 <049a01c13ffb$da851320$96c0b0d0@roweclan.net>
 <20010918135133.B9B7C46DFC@koj.rkbloom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010918135133.B9B7C46DFC@koj.rkbloom.net>
User-Agent: Mutt/1.3.20i

> Exactly, the client is still connected, but by this time, the client should have
> received all of the data.  The only thing we have is a connection that will be
> left open until both sides get around to closing it.  If a non-keepalive request
> is still receiving data after the log-transaction phase is run, then it is a bug in
> the server, and it should be fixed.

The client may still be sending data if it is pipelining requests and
the server has decided (due to error or choice) to close the connection
in the middle of the pipeline.  The server needs to keep the connnection
open long enough for the client to ack the receipt of the TCP segments
that contained the last server response.

As a protocol, this whole thing is lame -- it is caused because the TCP
socket API is broken in regards to close semantics.

....Roy