[
https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607536#action_12607536
]
indika priyantha kumara commented on SYNAPSE-368:
-------------------------------------------------
This issue can be resolved using existing synapse language API as follows
<property name="REMOTE_HOST" scope="axis2"
value="get-property('transport','X-Forwarded-For')"/>
The mediator you have provided, on the
http://esbsite.org/resources.jsp?path=/mediators/ziller/ReverseProxy ,can be
used for too.
Adding custom code to deal with custom headers may not be needed if there are
possible ways of doing those through synapse language API (Example : property ,
header mediators).
> 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]
