From: Mike Rumph Date: Fri, 1 Sep 2017 15:44:11 +0000 (+0000) Subject: Generated doc changes X-Git-Tag: 2.5.0-alpha~173 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=024ee22e5aa51ff208f9fbd4c35e20714644ee11;p=thirdparty%2Fapache%2Fhttpd.git Generated doc changes git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1806986 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_remoteip.html.en b/docs/manual/mod/mod_remoteip.html.en index 90bc1231d38..6ded973c1a3 100644 --- a/docs/manual/mod/mod_remoteip.html.en +++ b/docs/manual/mod/mod_remoteip.html.en @@ -85,7 +85,7 @@ via the request headers.
  • mod_authz_host
  • mod_status
  • mod_log_config
  • -
  • Proxy Protocol Spec
  • +
  • Proxy Protocol Spec
  • Comments
  • top
    @@ -235,23 +235,24 @@ RemoteIPProxiesHeader X-Forwarded-By Context:server config, virtual host Status:Base Module:mod_remoteip -Compatibility:RemoteIPProxyProtocol is only available in httpd 2.4.26 and newer +Compatibility:RemoteIPProxyProtocol is only available in httpd 2.4.28 and newer

    The RemoteIPProxyProtocol directive enables or disables the reading and handling of the PROXY protocol connection header. If enabled with the On flag, the upstream client must send the header every time it opens a connection or the connection will - be aborted unless it is in the list of disabled hosts provided by RemoteIPProxyProtocolExceptions + be aborted unless it is in the list of disabled hosts provided by the + RemoteIPProxyProtocolExceptions directive.

    While this directive may be specified in any virtual host, it is important to understand that because the PROXY protocol is connection based and protocol agnostic, the enabling and disabling is actually based - on ip-address and port. This means that if you have multiple name-based - virtual hosts for the same host and port, and you enable it any one of - them, then it is enabled for all them (with that host and port). It also + on IP address and port. This means that if you have multiple name-based + virtual hosts for the same host and port, and you enable it for any one of + them, then it is enabled for all of them (with that host and port). It also means that if you attempt to enable the PROXY protocol in one and disable - in the other, that won't work; in such a case the last one wins and a + in the other, that won't work; in such a case, the last one wins and a notice will be logged indicating which setting was being overridden.

    Listen 80
    @@ -286,7 +287,7 @@ Listen 8080
     Context:server config, virtual host
     Status:Base
     Module:mod_remoteip
    -Compatibility:RemoteIPProxyProtocolExceptions is only available in httpd 2.4.26 and newer
    +Compatibility:RemoteIPProxyProtocolExceptions is only available in httpd 2.4.28 and newer
     
         

    The RemoteIPProxyProtocol directive enables or disables the reading and handling of the PROXY protocol connection header. diff --git a/docs/manual/mod/mod_remoteip.xml.fr b/docs/manual/mod/mod_remoteip.xml.fr index fa47dda279f..d6164bb877f 100644 --- a/docs/manual/mod/mod_remoteip.xml.fr +++ b/docs/manual/mod/mod_remoteip.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_remoteip.xml.meta b/docs/manual/mod/mod_remoteip.xml.meta index 1a7c78a9f14..771852e80cd 100644 --- a/docs/manual/mod/mod_remoteip.xml.meta +++ b/docs/manual/mod/mod_remoteip.xml.meta @@ -8,6 +8,6 @@ en - fr + fr