Re: Using the x509HostnameVerifier option in http4
We are using apache-servicemix-4.3.0 and the different camel components are as given below. ./data/jbi/MYESBComp-sa/sus/MYESBComp-camel-su/lib/camel-http4-2.8.0.jar ./data/jbi/IDServerBus-sa/sus/IDServerBus-camel-su/lib/camel-jxpath-2.6.0.jar ./data/jbi/IDServerBus-sa/sus/IDServerBus-camel-su/lib/camel-http4-2.8.0.jar ./system/org/apache/servicemix/servicemix-camel/2011.01/servicemix-camel-2011.01.jar ./system/org/apache/camel/camel-blueprint/2.6.0/camel-blueprint-2.6.0.jar ./system/org/apache/camel/camel-spring/2.6.0/camel-spring-2.6.0.jar ./system/org/apache/camel/camel-core/2.6.0/camel-core-2.6.0.jar regards, Mohan -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5745523.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
As documented on [1], the option 'x509HostnameVerifier' is available from Camel 2.7.0. Apache ServiceMix 4.3.0 is using Apache Camel 2.6.0 [2]. You should not use Camel 2.8.0 in ServiceMix 4.3.0. Please consider to upgrade ServiceMix (also because Apache Camel 2.11.x is the oldest supported release at Apache). [1] http://camel.apache.org/http4.html [2] http://servicemix.apache.org/downloads/servicemix-4.3.0.html Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Sat, Jan 4, 2014 at 9:47 AM, Mohan mohann...@gmail.com wrote: We are using apache-servicemix-4.3.0 and the different camel components are as given below. ./data/jbi/MYESBComp-sa/sus/MYESBComp-camel-su/lib/camel-http4-2.8.0.jar ./data/jbi/IDServerBus-sa/sus/IDServerBus-camel-su/lib/camel-jxpath-2.6.0.jar ./data/jbi/IDServerBus-sa/sus/IDServerBus-camel-su/lib/camel-http4-2.8.0.jar ./system/org/apache/servicemix/servicemix-camel/2011.01/servicemix-camel-2011.01.jar ./system/org/apache/camel/camel-blueprint/2.6.0/camel-blueprint-2.6.0.jar ./system/org/apache/camel/camel-spring/2.6.0/camel-spring-2.6.0.jar ./system/org/apache/camel/camel-core/2.6.0/camel-core-2.6.0.jar regards, Mohan -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5745523.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
Which version of Camel do you use? Do you use multiple http endpoints? Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Thu, Jan 2, 2014 at 3:59 PM, Mohan mohann...@gmail.com wrote: Hi Xavier, I am kind of facing similar issue that you had faced earlier. I have added bean id=x509HostnameVerifier class=org.apache.http.conn.ssl.AllowAllHostnameVerifier / in my camel context and in the url, I have .to(https4://dummy?httpClient.soTimeout=6x509HostnameVerifier=x509HostnameVerifier); But even after that it kept on giving me exception for host name verification as it kept on using BrowserCompatHostnameVerifier Which also means that it did no honor the param in the URL or I did not give it correctly. Any pointers? regards, Mohan -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5745439.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
Hi Xavier, I am kind of facing similar issue that you had faced earlier. I have added bean id=x509HostnameVerifier class=org.apache.http.conn.ssl.AllowAllHostnameVerifier / in my camel context and in the url, I have .to(https4://dummy?httpClient.soTimeout=6x509HostnameVerifier=x509HostnameVerifier); But even after that it kept on giving me exception for host name verification as it kept on using BrowserCompatHostnameVerifier Which also means that it did no honor the param in the URL or I did not give it correctly. Any pointers? regards, Mohan -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5745439.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
Good to know it works for you. Have fun by riding the Camel, Christian On Tue, Jan 10, 2012 at 8:29 AM, xverges xver...@gmail.com wrote: Thanks, Christian. That helped me. I made my life hard by doing some typos and by creating the bean after I tried to use it, but thinks work now. bean id=hostnameVerifier class=org.apache.http.conn.ssl.AllowAllHostnameVerifier / camelContext xmlns=http://camel.apache.org/schema/spring; packagecom.ibm.bcn.xv/package /camelContext Thanks. -Xavier -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5133564.html Sent from the Camel - Users mailing list archive at Nabble.com.
Using the x509HostnameVerifier option in http4
I'm trying to use the x509HostnameVerifier option in an http4 uri from(jetty:https://0.0.0.0:4433/topython/?matchOnUriPrefix=true;) .to(https4://backend.fake.com:/?bridgeEndpoint=truethrowExceptionOnFailure=falsex509HostnameVerifier=AllowAllHostnameVerifier); but I'm getting an error No bean could be found in the registry for: AllowAllHostnameVerifier of type: org.apache.http.conn.ssl.X509HostnameVerifier Am I doing something wrong? I'm on version 2.9.0 Thanks in advance. -Xavier -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5131544.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
Hello Xavier! Could you share the Code how you set the host name verifier into the registry? You should do it as below: https://svn.apache.org/repos/asf/camel/trunk/components/camel-http4/src/test/java/org/apache/camel/component/http4/HttpsGetTest.java And of course, you can do it also with Spring. The bean id has to be used as value for the 'x509HostnameVerifier' option Best, Christian On Mon, Jan 9, 2012 at 4:28 PM, xverges xver...@gmail.com wrote: I'm trying to use the x509HostnameVerifier option in an http4 uri from(jetty:https://0.0.0.0:4433/topython/?matchOnUriPrefix=true;) .to(https4:// backend.fake.com:/?bridgeEndpoint=truethrowExceptionOnFailure=falsex509HostnameVerifier=AllowAllHostnameVerifier ); but I'm getting an error No bean could be found in the registry for: AllowAllHostnameVerifier of type: org.apache.http.conn.ssl.X509HostnameVerifier Am I doing something wrong? I'm on version 2.9.0 Thanks in advance. -Xavier -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5131544.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using the x509HostnameVerifier option in http4
Thanks, Christian. That helped me. I made my life hard by doing some typos and by creating the bean after I tried to use it, but thinks work now. bean id=hostnameVerifier class=org.apache.http.conn.ssl.AllowAllHostnameVerifier / camelContext xmlns=http://camel.apache.org/schema/spring; packagecom.ibm.bcn.xv/package /camelContext Thanks. -Xavier -- View this message in context: http://camel.465427.n5.nabble.com/Using-the-x509HostnameVerifier-option-in-http4-tp5131544p5133564.html Sent from the Camel - Users mailing list archive at Nabble.com.
