Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24931141.post@talk.nabble.com>
Date: Wed, 12 Aug 2009 00:10:36 -0700 (PDT)
From: Srivatsa Katta <vatsa.katta@gmail.com>
To: users@camel.apache.org
Subject: HTTP Status code propogation from HttpComponent
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi,

We have a scenario where we just have to intercept the calls between a http
server and the client.

So the route we have configured looks like this.

from("jetty:http://localhost:6666?matchOnUriPrefix=true").to("http://localhost:8899");

from("jetty:http://localhost:8899?matchOnUriPrefix=true").to("cxfbean:customerCXFService");

The client uses the jetty:http://localhost:6666 for any requests, we have to
intercept and the redirect the request to an other http server which is
jetty:http://localhost:8899, this application is kind of becoming a proxy
for an other web server.

The problem we have is, when the actual cxf service returns http status
codes like (200, 301, 404..) the same codes are not propagated back to the
original client. Bud did notice this behaviour, it propagates back all the
status codes with 2xx but for all other status codes it just returns http
status code as 500.

Is it a problem with http component ? or is it the expected behaviour of
http component. If so how do we get around this problem ?

Any help is appreciated.

Cheers!!
Katta
                

-- 
View this message in context: http://www.nabble.com/HTTP-Status-code-propogation-from-HttpComponent-tp24931141p24931141.html
Sent from the Camel - Users mailing list archive at Nabble.com.