From: Stefan Fritsch Date: Mon, 8 Nov 2010 20:49:47 +0000 (+0000) Subject: update transformation X-Git-Tag: 2.3.9~75 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=15cc720a1332f21019f6dc947386159473115ab1;p=thirdparty%2Fapache%2Fhttpd.git update transformation git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1032700 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_reqtimeout.html.en b/docs/manual/mod/mod_reqtimeout.html.en index 766d79d67af..e55eab947dd 100644 --- a/docs/manual/mod/mod_reqtimeout.html.en +++ b/docs/manual/mod/mod_reqtimeout.html.en @@ -75,6 +75,16 @@

+
  • + Usually, a server should have both header and body timeouts configured. + If a common configuration is used for http and https virtual hosts, the + timeouts should not be set too low: + +

    + RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500 +

    +
  • +
    top
    @@ -97,8 +107,13 @@ is sent.

    For SSL virtual hosts, the header timeout values include the time needed - to do the initial SSL handshake. The body timeout values include the time - needed for SSL renegotiation (if necessary).

    + 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 AcceptFilter is in use (usually the case on Linux and FreeBSD), the socket is not sent to the