Hello Lucien, 2017-04-08 17:28 GMT+02:00 Lucien Gentis <lucien.gen...@univ-lorraine.fr>:
> Hello, > > Trunk branch : mod_remoteip.xml file, > <name>RemoteIPProxyProtocolExceptions</name> > directive : > > "<usage> > <p>The <directive>RemoteIPProxyProtocol</directive> directive > enables or" > > must probably be replaced by : > > "<usage> > <p>The <directive>RemoteIPProxyProtocolExceptions</directive> > directive enables or" > I checked the last pending doc changes and the complete diff is: + <p>The <code class="directive">RemoteIPProxyProtocol</code> 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 + administrator to configure a single host or CIDR range of hosts that may do + so. This is generally useful for monitoring and administrative traffic to a + virtual host direct to the server behind the upstream load balancer.</p> + It may need to be explained a bit better but IIUC the paragraph is saying that since RemoteIPProxyProtocol is a on/off switch, RemoteIPProxyProtocolExceptions can be used to fine tune exceptions. > Same file : I'm not quite sure to understand the phrase "This is generally > useful for monitoring and administrative > traffic to a virtual host direct to the server behind the upstream load > balancer." > Definitely not clear, need a bit of rework. Do you have something in mind to fix it? Luca
