Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The title of this question is pretty self explanatory, but:

Does apaches keep alive timeout reset (as in, start again) every time a request is received?

So for example, assume we have a 60 second keep alive timeout:

Second 0 - First request recieved, keep alive starts - Timeout currently 60 seconds

Second 10 - Next request recieved, keep alive reset - Timeout currently 60 seconds

OR

Second 0 - First request recieved, keep alive starts - Timeout currently 60 seconds

Second 10 - Next request recieved, keep alive does not reset - Timeout currently 50 seconds

Thanks.

share|improve this question
add comment

1 Answer 1

Although this is unclear from the documentation, the timeout resets every time a response has been sent to the browser.

To be more exact, from the responses in this bug report we can see that the timeout actually (re)starts as soon as Apache has delivered its response to the underlying OS, although that distinction isn't important in most practical circumstances.

share|improve this answer
    
As soon as time allows, we will do some traffic sniffing and see what actually happens. We use apache behind nginx, and nginx now supports http/1.1 + keep alives when communicating to a backend server. Since our service is fairly busy, and we have a keep alive timeout (on the apache backend) of 120 seconds, in essence what should be happening is these connections should never "Connection: close". Will post update when testing done. Thanks! –  anonymous-one Aug 28 '12 at 12:59
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.