brother_of_karamazov
Legendary Poster
Anyone have an idea why Denver recommends the timeout in httpd.conf be set to some high number (2x WAS timeout)?
From the Apache docs:
The TimeOut directive currently defines the amount of time Apache will wait for three things:
1. The total amount of time it takes to receive a GET request.
2. The amount of time between receipt of TCP packets on a POST or PUT request.
3. The amount of time between ACKs on transmissions of TCP packets in responses.
The default in Apache is 300 seconds. Setting the timeout to a number Denver wants, like 4800 seconds (80 minutes) would only make Apache wait 80 minutes to process a GET, POST or PUT.
This doesn't seem to make sense. I have left it set to 300 seconds on several clients with no seeming ill effects. I'd just like to understand what Denver has in mind.
From the Apache docs:
The TimeOut directive currently defines the amount of time Apache will wait for three things:
1. The total amount of time it takes to receive a GET request.
2. The amount of time between receipt of TCP packets on a POST or PUT request.
3. The amount of time between ACKs on transmissions of TCP packets in responses.
The default in Apache is 300 seconds. Setting the timeout to a number Denver wants, like 4800 seconds (80 minutes) would only make Apache wait 80 minutes to process a GET, POST or PUT.
This doesn't seem to make sense. I have left it set to 300 seconds on several clients with no seeming ill effects. I'd just like to understand what Denver has in mind.