<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPHeader</directive> directive triggers
+ <p>The <directive>RemoteIPHeader</directive> directive triggers
<module>mod_remoteip</module> to treat the value of the specified
<var>header-field</var> header as the useragent IP address, or list
of intermediate useragent IP addresses, subject to further configuration
<note type="warning"> Unless these other directives are used, <module>mod_remoteip</module>
will trust all hosts presenting a non internal address in the
- <directive module="mod_remoteip">RemoteIPHeader</directive> header value.
+ <directive>RemoteIPHeader</directive> header value.
</note>
<example><title>Internal (Load Balancer) Example</title>
<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPInternalProxy</directive> directive adds one
+ <p>The <directive>RemoteIPInternalProxy</directive> directive adds one
or more addresses (or address blocks) to trust as presenting a valid
RemoteIPHeader value of the useragent IP. Unlike the
<directive module="mod_remoteip">RemoteIPTrustedProxy</directive> directive, any IP address
<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPInternalProxyList</directive> directive specifies
+ <p>The <directive>RemoteIPInternalProxyList</directive> 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 useragent IP.</p>
<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPProxiesHeader</directive> directive specifies
+ <p>The <directive>RemoteIPProxiesHeader</directive> directive specifies
a header into which <module>mod_remoteip</module> will collect a list of
all of the intermediate client IP addresses trusted to resolve the useragent
IP of the request. Note that intermediate
<compatibility>RemoteIPProxyProtocolExceptions is only available in httpd 2.4.31 and newer</compatibility>
<usage>
- <p>The <directive>RemoteIPProxyProtocol</directive> directive enables or
+ <p>The <directive>RemoteIPProxyProtocolExceptions</directive> directive enables or
disables the reading and handling of the PROXY protocol connection header.
Sometimes it is desirable to require clients to provide the PROXY header, but
permit other clients to connect without it. This directive allows a server
<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPTrustedProxy</directive>
+ <p>The <directive>RemoteIPTrustedProxy</directive>
directive restricts which peer IP addresses (or address blocks) will be
trusted to present a valid RemoteIPHeader value of the useragent IP.</p>
<contextlist><context>server config</context><context>virtual host</context></contextlist>
<usage>
- <p>The <directive module="mod_remoteip">RemoteIPTrustedProxyList</directive> directive specifies
+ <p>The <directive>RemoteIPTrustedProxyList</directive> 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 useragent IP.</p>