THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
You can append query options to the URI in the following format, ?option=value&option=value&...
| Info | ||
|---|---|---|
| ||
Notice Camel 2.2 or older uses the Apache HTTP Client 3.1. We upgraded to HTTP Client 4.0.1 in Camel 2.3. This has an impact if you need advanced configuration as these two versions is much different how you do that. Consult the HTTP Client 4.x documentation. |
| Info | ||
|---|---|---|
| ||
You can only produce to endpoints generated by the HTTP component. Therefore it should never be used as input into your camel Routes. To bind/expose an HTTP endpoint via a HTTP server as input to a camel route, you can use the Jetty Component |
...
Setting MaxConnectionsPerHost
Camel 2.2 or older
The Http Component has a org.apache.commons.httpclient.HttpConnectionManager where you can configure various global configuration for the given component.
By global, we mean that any endpoint the component creates has the same shared HttpConnectionManager. So, if we want to set a different value for the max connection per host, we need to define it on the HTTP component and not on the endpoint URI that we usually use. So here comes:
...
| Wiki Markup |
|---|
{snippet:id=e1|lang=xml|url=camel/trunk/tags/camel-2.2.0/tests/camel-itest/src/test/resources/org/apache/camel/itest/http/HttpMaxConnectionPerHostTest-context.xml} |
...
| Wiki Markup |
|---|
{snippet:id=e2|lang=xml|url=camel/trunk/tags/camel-2.2.0/tests/camel-itest/src/test/resources/org/apache/camel/itest/http/HttpMaxConnectionPerHostTest-context.xml} |
Camel 2.3 or newer
Consult the Apache HTTP Client 4.x documentation as HTTP Client 4.0 is configured much differently than the older 3.1.
Using HTTPS to authenticate gotchas
...