You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Olivier Ziller (JIRA)" <ji...@apache.org> on 2008/06/19 13:51:45 UTC
[jira] Created: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
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
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-368) IP address filter not
working when using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-368) IP address filter not
working when using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ 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:49 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" expression="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/resources.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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved SYNAPSE-368.
-------------------------------------
Resolution: Won't Fix
Extracting only the first IP address can probably be achieved using standard XPath functions. Otherwise a script, class or POJO mediator could be used.
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
indika priyantha kumara reassigned SYNAPSE-368:
-----------------------------------------------
Assignee: indika priyantha kumara
> 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
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
indika priyantha kumara resolved SYNAPSE-368.
---------------------------------------------
Resolution: Fixed
Fix Version/s: NIGHTLY
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Reopened: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "Olivier Ziller (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
indika priyantha kumara updated SYNAPSE-368:
--------------------------------------------
Comment: was deleted
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-368) IP address filter not working when
using an apache reverse proxy
Posted by "Olivier Ziller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609941#action_12609941 ]
Olivier Ziller commented on SYNAPSE-368:
----------------------------------------
thanks Indika
it worked using :
<syn:property name="REMOTE_ADDR" expression="get-property('transport','X-Forwarded-For')" scope="axis2"/>
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org