Re: httpclose/forceclose and TCP states

From: Chris Burroughs <chris.burroughs#gmail.com>
Date: Mon, 19 Sep 2011 11:21:51 -0400

On 09/08/2011 02:20 AM, Willy Tarreau wrote:
> On Tue, Sep 06, 2011 at 07:01:44PM -0400, Chris Burroughs wrote:

>> > On 09/01/2011 09:04 PM, Chris Burroughs wrote:
>>> > > I've looked at the source code and I think that's what's going on, but
>>> > > it has been a while since I've read C networking code.
>> > 
>> > If someone is in a particularly explanatory mood, I'm also trying to
>> > figure out how haproxy handles the SO_LINGER blocking/throws-away-data
>> > trap.  Apache httpd for example does this:
>> > https://github.com/apache/httpd/blob/trunk/server/connection.c#L43

> Those are complex issues and we had to perform some changes in the past.
> To make it short, by default the system handles "orphans", which are
> connections that have been closed but still have unacked data. This is
> very common with protocols working in question/response/close mode, as
> the server closes after sending the response.
>

...
> Regards,
> Willy
>

Thanks Willy, I found both of your responses helpful in figuring out what exactly is going on. Received on 2011/09/19 17:21