Add RemoteIP module support for behind LB
1 unresolved thread
1 unresolved thread
If REMOTEIP_INTERNAL_PROXY
is provided (usually a space separated list of proxy cidrs) then mod_remoteip is enabled.
This results in the REMOTE_HOST being obtained from the X-Forwarded-For
header, if available.
When processing the header (from right to left) any IPs in REMOTEIP_INTERNAL_PROXY
are skipped.
Closes: #39 (closed)
Edited by Robin Goodall
Merge request reports
Activity
Filter activity
changed milestone to %Sprint 101
mentioned in issue #39 (closed)
74 74 The container is available on Docker hub but may be built explicitly via the 75 75 usual ``docker build -t uisautomation/ucam-shib3-proxy .`` command issued in 76 76 the root of the repository. 77 78 ## Server URL and port 79 80 By default (unless using a SERVER_NAME of "localhost"), the SERVER_URL will be 81 set to "https://${SERVER_NAME}" and the SERVER_PORT will be "80". 82 83 Pass in your own values to override these. 84 85 ## Load balancer 86 87 If behind a load balancer then the Apache RemoteIP module can be used to resolve changed this line in version 2 of the diff
mentioned in commit 0cb5127e
Please register or sign in to reply