camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From santhosh <>
Subject Camel Http4 SSL/TLS configuring scheme port
Date Tue, 05 Mar 2013 16:01:05 GMT
i run camel in karaf.I use Http4 component for https connection with custom

Class connectionConfigurer{
SchemeRegistry registry = new SchemeRegistry();
registry.register(new Scheme("https", 443, new SSLSocketFactory(keystore,
"mypassword", truststore)));


So what happens when i do this

<to uri="https4://X:9090??httpClientConfigurer=CustomHttpClientConfigurer">
<to uri="https4://Y:9080??httpClientConfigurer=CustomHttpClientConfigurer">

i have registerd the scheme on 443 but the connection is to be made to 9090
and 9080.Will the keystore and truststore configured in connectionConfigurer
be used.Is it fine to do this??I saw the org.apache.http.conn.scheme.scheme
code and it says port param in constructor gets assigned to default and
there is a resolvePort(int port) function which defaults to default if the
passed param is invalid.How it does it work now.Does camel http4 component
call resolvePort() in org.apache.http.conn.scheme.scheme ??

I like custom HttpConfigurer but want to keep trust/keystore systemwide.I am
thinking of moving to karaf wide config for Keystore and truststore but i
have to think about functionality in customconfigurer in that case.I am
pretty much running on bundle/application wide custom SSL/TLS setting with
mulitple bundles having different customconfigurer but common
keystore/truststore.How much of a bad idea is it. 

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message