This directive can set various timeouts for receiving the request headers
and the request body from the client. If the client fails to send headers or
body within the configured time, a 408 REQUEST TIME OUT
error
is sent.
For SSL virtual hosts, the header timeout values include the time needed to do the initial SSL handshake. If the user's browser is configured to query certificate revocation lists and the CRL server is not reachable, the initial SSL handshake may take a significant time until the browser gives up waiting for the CRL. Therefore the header timeout values should not be set to very low values for SSL virtual hosts. The body timeout values include the time needed for SSL renegotiation (if necessary).
When an httpready
) is received. The header timeout configured with
RequestReadTimeout
is only effective after the server process has
received the socket.
For each of the two timeout types (header or body), there are three ways to specify the timeout:
The time in seconds allowed for reading all of the request headers or body, respectively. A value of 0 means no limit.
This disables
Same as above, but whenever data is received, the timeout value is increased according to the specified minimum data rate (in bytes per second).
Same as above, but the timeout will not be increased above the second value of the specified timeout range.