W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2009

Persistent connection timeout

From: Fred Bohle <Fred.Bohle@progress.com>
Date: Fri, 4 Dec 2009 10:59:07 -0500
Message-ID: <A8176F2E45B30247BBED3ED8A7CA63B3025BCEC0@MAIL03.bedford.progress.com>
To: <ietf-http-wg@w3.org>
 
    We support a web server on z/OS mainframes.  In this product, we
support HTTP 1.1 persistent connections.  We routinely return a response
with Connection: Keep-Alive headers.  If the connection remains idle for
a while, we simply close the connection.
 
    Now I am getting a request to change this behavior.  I am being
asked, after the idle timeout,  to send an EXTRA response, with a
Connection: Close header.  This seems odd to me.  Sending an extra
response seems like it introduces an instability:  If the client sends a
request at the same time as we are sending the extra response, the
client could think we processed the request, when we did not.
 
    How do other servers handle the idle connection timeout?  
 
Fred Bohle
Progress Software
Received on Friday, 4 December 2009 16:00:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:14 GMT