Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 31587 invoked from network); 22 Mar 2009 23:38:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Mar 2009 23:38:14 -0000 Received: (qmail 40939 invoked by uid 500); 22 Mar 2009 23:38:14 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 40856 invoked by uid 500); 22 Mar 2009 23:38:13 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 40848 invoked by uid 99); 22 Mar 2009 23:38:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Mar 2009 23:38:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Mar 2009 23:38:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0A143234C003 for ; Sun, 22 Mar 2009 16:37:51 -0700 (PDT) Message-ID: <1828113230.1237765071027.JavaMail.jira@brutus> Date: Sun, 22 Mar 2009 16:37:51 -0700 (PDT) From: "Andreas Veithen (JIRA)" To: dev@synapse.apache.org Subject: [jira] Resolved: (SYNAPSE-368) IP address filter not working when using an apache reverse proxy In-Reply-To: <531828232.1213876305058.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on 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