[ 
https://issues.apache.org/activemq/browse/CAMEL-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57791#action_57791
 ] 

Christian Mueller commented on CAMEL-1530:
------------------------------------------

Claus,
One notice: At beginning to implement/update httpClient, I created the Schema 
registry for http and https by default. The problem here was, that once created 
the 'org.apache.http.conn.ssl.SSLSocketFactory' with the static method 
'getSocketFactory()', it will reuse the underling 
'javax.net.ssl.SSLSocketFactory'. This means, that if the system properties 
'javax.net.ssl.*' is set after the first httpClient instance is created, these 
properties has no effect (Because the first camel-http tests uses http, I run 
into this trouble). That's the reason, why I only register the Schema which is 
used and not both (by default).

Should I do something (patch the tests in '/<camel_root>/tests')? Sorry for the 
incomplete patch... :-(

> Upgrade camel-http to use httpclient 4.0
> ----------------------------------------
>
>                 Key: CAMEL-1530
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1530
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-http
>    Affects Versions: 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Christian Mueller
>             Fix For: 2.3.0
>
>         Attachments: camel-gae_20100211.patch, camel-http.zip, 
> camel-http_20100211.patch, camel-jetty.zip, camel-jetty_20100211.patch, 
> camel-servlet_20100211.patch, localhost.ks
>
>          Time Spent: 4 weeks
>  Remaining Estimate: 0 minutes
>
> Upgrading httpclient from 3.1 to 4.0 requires changes in the camel-http code 
> as the API has change quite a lot.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to