[
https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Ziller reopened SYNAPSE-368:
------------------------------------
hello
just to say that the solution based on existing Synapse language API does not
works when you have multiple ip address separated by commas in the
X-Forwarded-For header (-Forwarded-For: 193.54.39.xx, 194.214.218.xx for
example)
it does happens when you pass within multiple reverse proxy before reaching
synapse.
best regards
> IP address filter not working when using an apache reverse proxy
> ----------------------------------------------------------------
>
> Key: SYNAPSE-368
> URL: https://issues.apache.org/jira/browse/SYNAPSE-368
> Project: Synapse
> Issue Type: Improvement
> Components: Extension Mediators
> Affects Versions: 1.1
> Environment: Linux RHEL 4
> Reporter: Olivier Ziller
> Assignee: indika priyantha kumara
> Fix For: NIGHTLY
>
>
> i use the throttle mediator in order restrict the use of a proxy to a
> particular ip address.
> all was working fine until i've put an apache reverse proxy in front of
> synapse.
> in this case, the ip address logged by Synapse is always the one of the
> reverse proxy.
> in fact, the real ip address of the caller is in the "X-Forwarded-For" http
> header (see http://httpd.apache.org/docs/2.2/mod/mod_proxy.html)
> Synapse seems not to take care of this http header...
> thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
