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. However, when Apache serves us a 302 redirect, it does NOT drop the connection, unless Connection: close is specified in the request headers. 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. Or is the 302-specific behaviour some kinda pre-keep-alive legacy behaviour? Elver --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|