Hi In Camel 2.3 we had upgraded camel-http to use Http Client 4.0.1.
But apparently it lacks some features which Http Client 3.1 has (something about setting preferred auth scheme, proxy and whatnot). Those options are not in HttpClient 4.0.1, but was added to HttpClient trunk, which is going on a long release plan as its going to be HttpClient 4.1.0. And HttpClient 4.1 is currently in alpha-2 release, which indicates a long release cycle. We cannot wait for that to happen, so we have change Camel trunk as follows: - camel-http = the good old trusty from Apache Camel 2.2 with Http Client 3.1 - camel-http4 = a new component using Http Client 4.0.1 for people who want to try out this - the other component which deps on camel-http (camel-servlet, camel-jetty, camel-gae) have been reverted to be able to use Http Client 3.1. That means Camel end users who upgrade to Apache Camel 2.3.0 release will not have to make any upgrades in their code if they were using any Http Client features which they had to use the Http Client API directly to do so. In the longer run we may let camel-http4 be the default http component when it has progressed and covers the use cases by the Camel end users. Notice: Apache cwiki is temporary out of service, so I cannot update the wiki pages about this. -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus