[
https://issues.apache.org/jira/browse/SLING-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3015.
-------------------------------------
Resolution: Won't Fix
> Take X-Forwarded-For into account for IP whitelisting
> -----------------------------------------------------
>
> Key: SLING-3015
> URL: https://issues.apache.org/jira/browse/SLING-3015
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.0
> Reporter: Stefan Egli
> Priority: Major
>
> Currently, the IP whitelisting for incoming topology connections of the
> discovery.impl uses 'getRequestHost/Addr' to decide if it wants to accept a
> connection or not. This is not sufficient in the case, where a server is
> behind eg a reverse proxy. In such cases it would simply get the reverse
> proxy's address, voiding the IP whitelisting feature.
> To improve this situation, the X-Forwarded-For header field should be
> evaluated optionally too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
