On Sep 19, 2008, at 11:33 AM, Dan Poirier wrote:
On Fri, September 19, 2008 11:18 am, Jim Jagielski wrote:
A better interpretation would be, I think, the number of keepalive
requests on that connection. So a '1' would be the 1st keepalive
request, 2 would be the 2nd, etc... So a '0' would be the
initial request, and would be applicable whether keepalives
are enabled or not. This would make the logic simpler.
That works. The remaining issue, which is minor, is that since
ap_set_keepalive() doesn't increment connection->keepalives on the
last request, the value logged will be N-1 for both the N-1 and N'th
keepalive request. But I don't imagine most connections will ever
see the N'th keepalive request.
Unless it is small, agreed... still, might be worthwhile to
handle it as you suggest anyway. :)
