[
https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607532#action_12607532
]
indika edited comment on SYNAPSE-368 at 6/24/08 2:47 AM:
--------------------------------------------------------------------------
This issue can be done through existing Synapse language API
Just adds the property mediator prior to handover message to throttle mediator
<property name="REMOTE_HOST" scope="axis2"
value="get-property('transport','X-Forwarded-For')"/>
The mdiator that you have provided on [1] , can be used too for this.
Adding custom code for handling custom headers may not be good if those can be
handled transparently through synapse language API (For example , header,
property mediators )
Thanks
Indika
[1] http://esbsite.org/resources.jsp?path=/mediators/ziller/ReverseProxy
was (Author: indika):
This issue can be done through existing Synapse language API
Just adds the property mediator prior to handover message to throttle mediator
<property name="REMOTE_HOST" scope="axis2"
value="get-property('transport','X-Forwarded-For')"/>
The mdiator that you have provided on [1] , can be used too for this.
Adding custom code for handling custom headers may not be good if those can be
handled transparently through synapse language API (For example , header,
property mediators )
Thanks
Indika
[1] http://esbsite.org/editor.jsp?path=/mediators/ziller/ReverseProxy
> 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]
