From: Luca Toscano Date: Mon, 9 Dec 2019 09:28:43 +0000 (+0000) Subject: Documentation rebuild X-Git-Tag: 2.5.0-alpha2-ci-test-only~1758 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=940ba678d2200172e90e29e57a85a5dd3a7ec492;p=thirdparty%2Fapache%2Fhttpd.git Documentation rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1871080 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index a1222ce3437..fd6dc9e7503 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -783,7 +783,7 @@ NoProxy .example.com 192.168.112.0/21 Context:server config, virtual host, directory Status:Extension Module:mod_proxy -Compatibility:Available in version 2.4.39 and later +Compatibility:Available in version 2.4.40 and later

This directive determines whether the proxy should forward 100-continue Expect:ation to the origin server and thus let it decide when/if @@ -1006,7 +1006,7 @@ proxied resources

top

ProxyMaxForwards Directive

- @@ -2085,7 +2085,7 @@ expressions
Description:Maximium number of proxies that a request can be forwarded +
Description:Maximum number of proxies that a request can be forwarded through
Syntax:ProxyMaxForwards number
Default:ProxyMaxForwards -1
Status:Extension
Module:mod_proxy
-

This directive allows a user to specifiy a timeout on proxy requests. +

This directive allows a user to specify a timeout on proxy requests. This is useful when you have a slow/buggy appserver which hangs, and you would rather just return a timeout and fail gracefully instead of waiting however long it takes the server to return.

diff --git a/docs/manual/mod/mod_proxy.xml.fr b/docs/manual/mod/mod_proxy.xml.fr index 493a303cbbf..b084f5833c4 100644 --- a/docs/manual/mod/mod_proxy.xml.fr +++ b/docs/manual/mod/mod_proxy.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja index e5396d237aa..ac0c9c01436 100644 --- a/docs/manual/mod/mod_proxy.xml.ja +++ b/docs/manual/mod/mod_proxy.xml.ja @@ -1,7 +1,7 @@ - + + diff --git a/docs/manual/mod/mod_rewrite.xml.meta b/docs/manual/mod/mod_rewrite.xml.meta index decc0a7b1e8..0be21e86f4d 100644 --- a/docs/manual/mod/mod_rewrite.xml.meta +++ b/docs/manual/mod/mod_rewrite.xml.meta @@ -8,6 +8,6 @@ en - fr + fr diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en index 4bb642c2872..bac5512335f 100644 --- a/docs/manual/mod/mod_ssl.html.en +++ b/docs/manual/mod/mod_ssl.html.en @@ -2446,7 +2446,7 @@ should be shared between multiple nodes. For single-instance httpd setups, it is recommended to not configure a ticket key file, but to rely on (random) keys generated by mod_ssl at startup, instead.

The ticket key file must contain 48 bytes of random data, -preferrably created from a high-entropy source. On a Unix-based system, +preferably created from a high-entropy source. On a Unix-based system, a ticket key file can be created as follows:

@@ -2534,7 +2534,7 @@ utility:

openssl srp -srpvfile passwd.srpv -userinfo "some info" -add username

The value given with the optional -userinfo parameter is -avalable in the SSL_SRP_USERINFO request environment variable.

+available in the SSL_SRP_USERINFO request environment variable.

diff --git a/docs/manual/mod/mod_ssl.xml.es b/docs/manual/mod/mod_ssl.xml.es index a12f0eb0782..377b6d9ea90 100644 --- a/docs/manual/mod/mod_ssl.xml.es +++ b/docs/manual/mod/mod_ssl.xml.es @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_ssl.xml.fr b/docs/manual/mod/mod_ssl.xml.fr index 3843fdc4b8c..13c9cc5e463 100644 --- a/docs/manual/mod/mod_ssl.xml.fr +++ b/docs/manual/mod/mod_ssl.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_ssl.xml.meta b/docs/manual/mod/mod_ssl.xml.meta index d50eb9de390..194507ef078 100644 --- a/docs/manual/mod/mod_ssl.xml.meta +++ b/docs/manual/mod/mod_ssl.xml.meta @@ -9,6 +9,6 @@ en es - fr + fr