diff --git a/docs/manual/developer/new_api_2_4.html.en b/docs/manual/developer/new_api_2_4.html.en index b5aad94b58..6a4c68cd32 100644 --- a/docs/manual/developer/new_api_2_4.html.en +++ b/docs/manual/developer/new_api_2_4.html.en @@ -153,9 +153,9 @@
conn_rec->remote_ip and conn_rec->remote_addr
mod_proxy
Description: | Replaces the original peer IP address for the connection
-with the client IP address list presented by a proxies or a load balancer
+
Summary-This module is used to treat the client which initiated the - request as the originating client as identified by httpd for the - purposes of authorization and logging, even where that client is + This module is used to treat the useragent which initiated the + request as the originating useragent as identified by httpd for the + purposes of authorization and logging, even where that useragent is behind a load balancer, front end server, or proxy server. -The module overrides the peer IP address for the connection - with the client IP address reported in the request header configured + The module overrides the client IP address for the connection
+ with the useragent IP address reported in the request header configured
with the Once replaced as instructed, this overridden client IP address is + Once replaced as instructed, this overridden useragent IP address is
then used for the It is critical to only enable this behavior from
intermediate hosts (proxies, etc) which are trusted by this server, since
- it is trivial for the remote client to impersonate another client.
+ it is trivial for the remote useragent to impersonate another
+ useragent.
Directives
Remote IP Processing-Apache by default identifies the client with the connection's - peer_ip value, and the connection remote_host and remote_logname are + Apache by default identifies the useragent with the connection's + client_ip value, and the connection remote_host and remote_logname are derived from this value. These fields play a role in authentication, authorization and logging and other purposes by other loadable modules. -mod_remoteip overrides the peer IP of the connection with the - advertised client IP as provided by a proxy or load balancer, for + mod_remoteip overrides the client IP of the connection with the + advertised useragent IP as provided by a proxy or load balancer, for the duration of the request. A load balancer might establish a long lived keepalive connection with the server, and each request will - have the correct client IP, even though the underlying peer IP + have the correct useragent IP, even though the underlying client IP address of the load balancer remains unchanged. -When multiple, comma delimited client IP addresses are listed in the + When multiple, comma delimited useragent IP addresses are listed in the header value, they are processed in Right-to-Left order. Processing - halts when a given client IP address is not trusted to present the + halts when a given useragent IP address is not trusted to present the preceding IP address. The header field is updated to this remaining list of unconfirmed IP addresses, or if all IP addresses were trusted, this header is removed from the request altogether. @@ -117,7 +118,7 @@ via the request headers.RemoteIPHeader Directive
The |
---|
The RemoteIPInternalProxy
directive adds one
or more addresses (or address blocks) to trust as presenting a valid
- RemoteIPHeader value of the client IP. Unlike the
+ RemoteIPHeader value of the useragent IP. Unlike the
RemoteIPTrustedProxy
directive, any IP address
presented in this header, including private intranet addresses, are
trusted when passed from these proxies.
The RemoteIPInternalProxyList
directive specifies
a file parsed at startup, and builds a list of addresses (or address blocks)
- to trust as presenting a valid RemoteIPHeader value of the client IP.
The '#
' hash character designates a comment line, otherwise
each whitespace or newline separated entry is processed identically to
@@ -204,7 +205,7 @@ via the request headers.
The RemoteIPProxiesHeader
directive specifies
a header into which mod_remoteip
will collect a list of
- all of the intermediate client IP addresses trusted to resolve the client
+ all of the intermediate client IP addresses trusted to resolve the useragent
IP of the request. Note that intermediate
RemoteIPTrustedProxy
addresses are recorded in
this header, while any intermediate
@@ -227,11 +228,11 @@ via the request headers.
The RemoteIPTrustedProxy
directive adds one
or more addresses (or address blocks) to trust as presenting a valid
- RemoteIPHeader value of the client IP. Unlike the
+ RemoteIPHeader value of the useragent IP. Unlike the
RemoteIPInternalProxy
directive, any intranet
or private IP address reported by such proxies, including the 10/8, 172.16/12,
192.168/16, 169.254/16 and 127/8 blocks (or outside of the IPv6 public
- 2000::/3 block) are not trusted as the client IP, and are left in the
+ 2000::/3 block) are not trusted as the useragent IP, and are left in the
RemoteIPHeader
header's value.
The
@@ -252,7 +253,7 @@ via the request headers.
RemoteIPTrustedProxyList
directive specifies
a file parsed at startup, and builds a list of addresses (or address blocks)
- to trust as presenting a valid RemoteIPHeader value of the client IP.
The '#
' hash character designates a comment line, otherwise
each whitespace or newline seperated entry is processed identically to
diff --git a/docs/manual/mod/quickreference.html.en b/docs/manual/mod/quickreference.html.en
index fcf0825dca..e03639c6b4 100644
--- a/docs/manual/mod/quickreference.html.en
+++ b/docs/manual/mod/quickreference.html.en
@@ -704,7 +704,7 @@ a different URL