Background. We're writing a HTTP client. We don't yet have support for
keep-alive, so we don't set any keep-alive specific headers
(connection, keep-alive).
Now, when Apache serves us a page, it drops the connection after
serving it. Which is what one would expect if we don't set keep-alive.
On 3/25/06, Elver Loho [EMAIL PROTECTED] wrote:
Background. We're writing a HTTP client. We don't yet have support for
keep-alive, so we don't set any keep-alive specific headers
(connection, keep-alive).
Now, when Apache serves us a page, it drops the connection after
serving it. Which is
On Saturday 25 March 2006 23:03, Elver Loho wrote:
I'm not sure how the RFC specifies this, but I kinda expect Apache to
default to assuming Connection: close when no keep-alive is specified.
HTTP/1.0 defaults to closing the connection. HTTP/1.1 defaults to
keeping it open. But those are
