On Sep 8, 2008, at 9:26 AM, Dan Poirier wrote:
I've noticed that when MaxKeepAliveRequests is set to N, each connection handles up to N+1 requests. To me this seemed surprising, but a co-worker interprets MaxKeepAliveRequests as the number of additional requests served due to KeepAlive, which would make this exactly right. I'm wondering what the consensus is about the intention here. Perhaps the doc could be clarified.
The initial request is not a keepalive request. If I make 1 initial request, and then another on the same socket, then the 2nd request is the 1st keepalive request.
