Using jetty in both sides it works fine. Thanks. But, I'm using jetty:https also in the consumer side.
<endpoint id="camel"> uri="jetty:http://0.0.0.0:8080/camel?matchOnUriPrefix=true&bridgeEndpoint=true"/> <endpoint id="camel-https"> uri="jetty:https://0.0.0.0:8080/camel?matchOnUriPrefix=true&bridgeEndpoint=true"/> <endpoint id="system"> uri="jetty:http://10.112.27.150:8080/system?bridgeEndpoint=true&throwExceptionOnFailure=true"/> I need to add this endpoint? <endpoint id="system-https"> uri="jetty:https://10.112.27.150:8080/system?bridgeEndpoint=true&throwExceptionOnFailure=true"/> With http4 in the producer endpoint, entering via jetty:http or jetty:https it worked fine going to (only one) http4 (I presume it assumed http ou https according with the source request) endpoint. -----Original Message----- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: quinta-feira, 17 de Novembro de 2011 10:37 To: users@camel.apache.org Subject: Re: Apache Camel 2.6.0 to 2.8.2 http4 problem Try using jetty on the producer side as well as Jetty supports both, and they are fully async, which scales better. But you may have found some odd issue. Can you try with the 2.9.0-RC1 release as well? On Thu, Nov 17, 2011 at 11:27 AM, Carlos Manuel Figueiredo <carlos-m-figueir...@ext.ptinovacao.pt> wrote: > I'm upgrading from Apache Camel 2.6.0 to 2.8.2 and I'm having a problem. > > Before the upgrade e manage to redirect a request from this > > <endpoint id="camel" > uri="jetty:http://0.0.0.0:8080/camel?matchOnUriPrefix=true&bridgeE > ndpoint=true"/> > > to this > > <endpoint id="system" > uri="http4://10.112.27.150:8080/system?bridgeEndpoint=true&throwEx > ceptionOnFailure=true"/> > > using a simple > > .choice() > .when(header("CamelHttpUri").regex(".*/(resource).*")) > .to("system") > > but after the upgrade, the final URI passed from <a > href="http://host:port/system/resource";>http://host:port/system/resour > ce to <a > href="http://host:port/system?bridgeEndpoint=true&throwExceptionOnFail > ure=true/resource">http://host:port/system?bridgeEndpoint=true&throwEx > ceptionOnFailure=true/resource > > It's not replacing "?bridgeEndpoint=true&throwExceptionOnFailure=true" > correctly > > Any ideias? Is this a bug from the new version? > > Best regards, > Carlos > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
