HTTP
Since Camel 2.3
Only producer is supported
The HTTP component provides HTTP based endpoints for calling external HTTP resources (as a client to call external servers using HTTP).
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-http</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
URI format
http:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL as a type safe way of configuring endpoints.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The HTTP component supports 37 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
To use a custom org.apache.http.client.CookieStore. By default the org.apache.http.impl.client.BasicCookieStore is used which is an in-memory only cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn’t be stored as we are just bridging (eg acting as a proxy). |
CookieStore |
||
If this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Setting this to false, allows to only include the headers from the HTTP response (not propagating IN headers). |
true |
boolean |
|
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
|
This threshold in bytes controls whether the response payload should be stored in memory as a byte array or be streaming based. Set this to -1 to always use streaming mode. |
8192 |
int |
|
Whether to skip mapping all the Camel headers as HTTP request headers. If there are no data from Camel headers needed to be included in the HTTP request then this can avoid parsing overhead with many object allocations for the JVM garbage collector. |
false |
boolean |
|
Whether to skip mapping all the HTTP response headers to Camel headers. If there are no data needed from HTTP headers then this can avoid parsing overhead with many object allocations for the JVM garbage collector. |
false |
boolean |
|
Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. |
false |
boolean |
|
Disables authentication scheme caching. |
false |
boolean |
|
Disables automatic request recovery and re-execution. |
false |
boolean |
|
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
|
To use a custom and shared HttpClientConnectionManager to manage connections. If this has been configured then this is always used for all endpoints created by this component. |
HttpClientConnectionManager |
||
The maximum number of connections per route. |
20 |
int |
|
Disables connection state tracking. |
false |
boolean |
|
The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
long |
||
Disables automatic content decompression. |
false |
boolean |
|
Disables state (cookie) management. |
false |
boolean |
|
Disables the default user agent set by this builder if none has been provided by the user. |
false |
boolean |
|
To use a custom HttpBinding to control the mapping between Camel message and HttpClient. |
HttpBinding |
||
To use the custom HttpClientConfigurer to perform configuration of the HttpClient that will be used. |
HttpClientConfigurer |
||
To use the shared HttpConfiguration as base configuration. |
HttpConfiguration |
||
To use a custom org.apache.http.protocol.HttpContext when executing requests. |
HttpContext |
||
The maximum number of connections. |
200 |
int |
|
Disables automatic redirect handling. |
false |
boolean |
|
To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. |
HeaderFilterStrategy |
||
Proxy authentication domain to use. |
String |
||
Proxy authentication host. |
String |
||
Proxy authentication method to use. Enum values:
|
String |
||
Proxy authentication domain (workstation name) to use with NTML. |
String |
||
Proxy authentication password. |
String |
||
Proxy authentication port. |
Integer |
||
Proxy authentication username. |
String |
||
To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.support.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. |
SSLContextParameters |
||
Enable usage of global SSL context parameters. |
false |
boolean |
|
To use a custom X509HostnameVerifier such as DefaultHostnameVerifier or NoopHostnameVerifier. |
HostnameVerifier |
||
The timeout in milliseconds used when requesting a connection from the connection manager. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). |
-1 |
int |
|
Determines the timeout in milliseconds until a connection is established. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). |
-1 |
int |
|
Defines the socket timeout in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). |
-1 |
int |
Endpoint Options
The HTTP endpoint is configured using URI syntax:
http://httpUri
with the following path and query parameters:
Path Parameters (1 parameters)
Name | Description | Default | Type |
---|---|---|---|
Required The url of the HTTP endpoint to call. |
URI |
Query Parameters (48 parameters)
Name | Description | Default | Type |
---|---|---|---|
Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. If you use Servlet to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. The http producer will by default cache the response body stream. If setting this option to true, then the producers will not cache the response body stream but use the response stream as-is as the message body. |
false |
boolean |
|
To use a custom HeaderFilterStrategy to filter header to and from Camel message. |
HeaderFilterStrategy |
||
If the option is true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint’s URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back. |
false |
boolean |
|
Whether to clear expired cookies before sending the HTTP request. This ensures the cookies store does not keep growing by adding new cookies which is newer removed when they are expired. If the component has disabled cookie management then this option is disabled too. |
true |
boolean |
|
Specifies whether a Connection Close header must be added to HTTP Request. By default connectionClose is false. |
false |
boolean |
|
If this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Setting this to false, allows to only include the headers from the HTTP response (not propagating IN headers). |
true |
boolean |
|
To use custom host header for producer. When not set in query will be ignored. When set will override host header derived from url. |
String |
||
Configure the HTTP method to use. The HttpMethod header cannot override this option if set. Enum values:
|
HttpMethods |
||
If this option is true, The http producer won’t read response body and cache the input stream. |
false |
boolean |
|
If the option is true, HttpProducer will set the Host header to the value contained in the current exchange Host header, useful in reverse proxy applications where you want the Host header received by the downstream server to reflect the URL called by the upstream client, this allows applications which use the Host header to generate accurate URL’s for a proxied service. |
false |
boolean |
|
Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. |
true |
boolean |
|
Configure a cookie handler to maintain a HTTP session. |
CookieHandler |
||
To use a custom CookieStore. By default the BasicCookieStore is used which is an in-memory only cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn’t be stored as we are just bridging (eg acting as a proxy). If a cookieHandler is set then the cookie store is also forced to be a noop cookie store as cookie handling is then performed by the cookieHandler. |
CookieStore |
||
Whether the HTTP DELETE should include the message body or not. By default HTTP DELETE do not include any HTTP body. However in some rare cases users may need to be able to include the message body. |
false |
boolean |
|
Whether the HTTP GET should include the message body or not. By default HTTP GET do not include any HTTP body. However in some rare cases users may need to be able to include the message body. |
false |
boolean |
|
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
|
The status codes which are considered a success response. The values are inclusive. Multiple ranges can be defined, separated by comma, e.g. 200-204,209,301-304. Each range must be a single number or from-to with the dash included. |
200-299 |
String |
|
Whether to skip mapping all the Camel headers as HTTP request headers. If there are no data from Camel headers needed to be included in the HTTP request then this can avoid parsing overhead with many object allocations for the JVM garbage collector. |
false |
boolean |
|
Whether to skip mapping all the HTTP response headers to Camel headers. If there are no data needed from HTTP headers then this can avoid parsing overhead with many object allocations for the JVM garbage collector. |
false |
boolean |
|
To set a custom HTTP User-Agent request header. |
String |
||
Provide access to the http client request parameters used on new RequestConfig instances used by producers or consumers of this endpoint. |
HttpClientBuilder |
||
To use a custom HttpClientConnectionManager to manage connections. |
HttpClientConnectionManager |
||
The maximum number of connections per route. |
20 |
int |
|
Sets a custom HttpClient to be used by the producer. |
HttpClient |
||
Register a custom configuration strategy for new HttpClient instances created by producers or consumers such as to configure authentication mechanisms etc. |
HttpClientConfigurer |
||
To configure the HttpClient using the key/values from the Map. |
Map |
||
To use a custom HttpContext instance. |
HttpContext |
||
The maximum number of connections. |
200 |
int |
|
To use System Properties as fallback for configuration. |
false |
boolean |
|
Proxy authentication domain to use with NTML. |
String |
||
Proxy authentication host. |
String |
||
Proxy authentication method to use. Enum values:
|
String |
||
Proxy authentication domain (workstation name) to use with NTML. |
String |
||
Proxy authentication password. |
String |
||
Proxy authentication port. |
int |
||
Proxy authentication scheme to use. Enum values:
|
String |
||
Proxy authentication username. |
String |
||
Proxy hostname to use. |
String |
||
Proxy port to use. |
int |
||
Authentication domain to use with NTML. |
String |
||
If this option is true, camel-http sends preemptive basic authentication to the server. |
false |
boolean |
|
Authentication host to use with NTML. |
String |
||
Authentication methods allowed to use as a comma separated list of values Basic, Digest or NTLM. |
String |
||
Which authentication method to prioritize to use, either as Basic, Digest or NTLM. Enum values:
|
String |
||
Authentication password. |
String |
||
Authentication username. |
String |
||
To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.util.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. |
SSLContextParameters |
||
To use a custom X509HostnameVerifier such as DefaultHostnameVerifier or NoopHostnameVerifier. |
HostnameVerifier |
Message Headers
The HTTP component supports 14 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
Constant: |
The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as gzip. |
String |
|
CamelHttpResponseCode (producer) Constant: |
The HTTP response code from the external server. Is 200 for OK. |
int |
|
CamelHttpResponseText (producer) Constant: |
The HTTP response text from the external server. |
String |
|
Constant: |
URI parameters. Will override existing URI parameters set directly on the endpoint. |
String |
|
CamelHttpProtocolVersion (producer) Constant: |
The version of the http protocol used. |
String |
|
Constant: |
The target host. |
String |
|
Constant: |
The rest http URI. |
String |
|
Constant: |
URI to call. Will override existing URI set directly on the endpoint. This uri is the uri of the http server to call. Its not the same as the Camel endpoint uri, where you can configure endpoint options such as security etc. This header does not support that, its only the uri of the http server. |
String |
|
Constant: |
Request URI’s path, the header will be used to build the request URI with the HTTP_URI. |
String |
|
Constant: |
The rest http query. |
String |
|
Constant: |
The http raw query. |
String |
|
Constant: |
The http method to use. Enum values:
|
HttpMethods |
|
CamelHttpCharacterEncoding (producer) Constant: |
The character encoding. |
String |
|
Constant: |
The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as text/html. |
String |
Message Body
Camel will store the HTTP response from the external server on the OUT body. All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally, Camel will add the HTTP response headers as well to the OUT message headers.
Using System Properties
When setting useSystemProperties to true, the HTTP Client will look for the following System Properties and it will use it:
-
ssl.TrustManagerFactory.algorithm
-
javax.net.ssl.trustStoreType
-
javax.net.ssl.trustStore
-
javax.net.ssl.trustStoreProvider
-
javax.net.ssl.trustStorePassword
-
java.home
-
ssl.KeyManagerFactory.algorithm
-
javax.net.ssl.keyStoreType
-
javax.net.ssl.keyStore
-
javax.net.ssl.keyStoreProvider
-
javax.net.ssl.keyStorePassword
-
http.proxyHost
-
http.proxyPort
-
http.nonProxyHosts
-
http.keepAlive
-
http.maxConnections
Response code
Camel will handle according to the HTTP response code:
-
Response code is in the range 100..299, Camel regards it as a success response.
-
Response code is in the range 300..399, Camel regards it as a redirection response and will throw a
HttpOperationFailedException
with the information. -
Response code is 400+, Camel regards it as an external server failure and will throw a
HttpOperationFailedException
with the information.
throwExceptionOnFailure
The option, throwExceptionOnFailure
, can be set to false
to prevent
the HttpOperationFailedException
from being thrown for failed response
codes. This allows you to get any response from the remote server.
Exceptions
HttpOperationFailedException
exception contains the following information:
-
The HTTP status code
-
The HTTP status line (text of the status code)
-
Redirect location, if server returned a redirect
-
Response body as a
java.lang.String
, if server provided a body as response
Which HTTP method will be used
The following algorithm is used to determine what HTTP method should be used:
1. Use method provided as endpoint configuration (httpMethod
).
2. Use method provided in header (Exchange.HTTP_METHOD
).
3. GET
if query string is provided in header.
4. GET
if endpoint is configured with a query string.
5. POST
if there is data to send (body is not null
).
6. GET
otherwise.
Configuring URI to call
You can set the HTTP producer’s URI directly from the endpoint URI. In
the route below, Camel will call out to the external server, oldhost
,
using HTTP.
from("direct:start")
.to("http://oldhost");
And the equivalent XML DSL:
<route>
<from uri="direct:start"/>
<to uri="http://oldhost"/>
</route>
You can override the HTTP endpoint URI by adding a header with the key
Exchange.HTTP_URI
on the message.
from("direct:start")
.setHeader(Exchange.HTTP_URI, constant("http://newhost"))
.to("http://oldhost");
In the sample above Camel will call the http://newhost despite the
endpoint is configured with http://oldhost.
If the http endpoint is working in bridge mode, it will ignore the
message header of Exchange.HTTP_URI
.
Configuring URI Parameters
The http producer supports URI parameters to be sent to the HTTP
server. The URI parameters can either be set directly on the endpoint
URI or as a header with the key Exchange.HTTP_QUERY
on the message.
from("direct:start")
.to("http://oldhost?order=123&detail=short");
Or options provided in a header:
from("direct:start")
.setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short"))
.to("http://oldhost");
How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
The HTTP component provides a way to set the HTTP request method by setting the message header. Here is an example:
from("direct:start")
.setHeader(Exchange.HTTP_METHOD, constant(org.apache.camel.component.http.HttpMethods.POST))
.to("http://www.google.com")
.to("mock:results");
The method can be written a bit shorter using the string constants:
.setHeader("CamelHttpMethod", constant("POST"))
And the equivalent XML DSL:
<route>
<from uri="direct:start"/>
<setHeader name="CamelHttpMethod">
<constant>POST</constant>
</setHeader>
<to uri="http://www.google.com"/>
<to uri="mock:results"/>
</route>
Using client timeout - SO_TIMEOUT
See the HttpSOTimeoutTest unit test.
Configuring a Proxy
The HTTP component provides a way to configure a proxy.
from("direct:start")
.to("http://oldhost?proxyAuthHost=www.myproxy.com&proxyAuthPort=80");
There is also support for proxy authentication via the
proxyAuthUsername
and proxyAuthPassword
options.
Using proxy settings outside of URI
To avoid System properties conflicts, you can set proxy configuration
only from the CamelContext or URI.
Java DSL :
context.getGlobalOptions().put("http.proxyHost", "172.168.18.9");
context.getGlobalOptions().put("http.proxyPort", "8080");
Spring XML
<camelContext>
<properties>
<property key="http.proxyHost" value="172.168.18.9"/>
<property key="http.proxyPort" value="8080"/>
</properties>
</camelContext>
Camel will first set the settings from Java System or CamelContext Properties and then the endpoint proxy options if provided. So you can override the system properties with the endpoint options.
There is also a http.proxyScheme
property you
can set to explicit configure the scheme to use.
Configuring charset
If you are using POST
to send data you can configure the charset
using the Exchange
property:
exchange.setProperty(Exchange.CHARSET_NAME, "ISO-8859-1");
Sample with scheduled poll
This sample polls the Google homepage every 10 seconds and write the
page to the file message.html
:
from("timer://foo?fixedRate=true&delay=0&period=10000")
.to("http://www.google.com")
.setHeader(FileComponent.HEADER_FILE_NAME, "message.html")
.to("file:target/google");
URI Parameters from the endpoint URI
In this sample we have the complete URI endpoint that is just what you
would have typed in a web browser. Multiple URI parameters can of course
be set using the &
character as separator, just as you would in the
web browser. Camel does no tricks here.
// we query for Camel at the Google page
template.sendBody("http://www.google.com/search?q=Camel", null);
URI Parameters from the Message
Map headers = new HashMap();
headers.put(Exchange.HTTP_QUERY, "q=Camel&lr=lang_en");
// we query for Camel and English language at Google
template.sendBody("http://www.google.com/search", null, headers);
In the header value above notice that it should not be prefixed with
?
and you can separate parameters as usual with the &
char.
Getting the Response Code
You can get the HTTP response code from the HTTP component by getting
the value from the Out message header with
Exchange.HTTP_RESPONSE_CODE
.
Exchange exchange = template.send("http://www.google.com/search", new Processor() {
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(Exchange.HTTP_QUERY, constant("hl=en&q=activemq"));
}
});
Message out = exchange.getOut();
int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
Disabling Cookies
To disable cookies you can set the HTTP Client to ignore cookies by
adding this URI option: httpClient.cookieSpec=ignoreCookies
Basic auth with the streaming message body
In order to avoid the NonRepeatableRequestException
, you need to do the
Preemptive Basic Authentication by adding the option: authenticationPreemptive=true
Advanced Usage
If you need more control over the HTTP producer you should use the
HttpComponent
where you can set various classes to give you custom
behavior.
Setting up SSL for HTTP Client
Using the JSSE Configuration Utility
The HTTP component supports SSL/TLS configuration through the Camel JSSE Configuration Utility. This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels. The following examples demonstrate how to use the utility with the HTTP component.
Programmatic configuration of the component
KeyStoreParameters ksp = new KeyStoreParameters();
ksp.setResource("/users/home/server/keystore.jks");
ksp.setPassword("keystorePassword");
KeyManagersParameters kmp = new KeyManagersParameters();
kmp.setKeyStore(ksp);
kmp.setKeyPassword("keyPassword");
SSLContextParameters scp = new SSLContextParameters();
scp.setKeyManagers(kmp);
HttpComponent httpComponent = getContext().getComponent("https", HttpComponent.class);
httpComponent.setSslContextParameters(scp);
Spring DSL based configuration of endpoint
<camel:sslContextParameters
id="sslContextParameters">
<camel:keyManagers
keyPassword="keyPassword">
<camel:keyStore
resource="/users/home/server/keystore.jks"
password="keystorePassword"/>
</camel:keyManagers>
</camel:sslContextParameters>
<to uri="https://127.0.0.1/mail/?sslContextParameters=#sslContextParameters"/>
Configuring Apache HTTP Client Directly
Basically camel-http component is built on the top of
Apache HttpClient.
Please refer to
SSL/TLS
customization for details or have a look into the
org.apache.camel.component.http.HttpsServerTestSupport
unit test base
class.
You can also implement a custom
org.apache.camel.component.http.HttpClientConfigurer
to do some
configuration on the http client if you need full control of it.
However if you just want to specify the keystore and truststore you
can do this with Apache HTTP HttpClientConfigurer
, for example:
KeyStore keystore = ...;
KeyStore truststore = ...;
SchemeRegistry registry = new SchemeRegistry();
registry.register(new Scheme("https", 443, new SSLSocketFactory(keystore, "mypassword", truststore)));
And then you need to create a class that implements
HttpClientConfigurer
, and registers https protocol providing a
keystore or truststore per example above. Then, from your camel route
builder class you can hook it up like so:
HttpComponent httpComponent = getContext().getComponent("http", HttpComponent.class);
httpComponent.setHttpClientConfigurer(new MyHttpClientConfigurer());
If you are doing this using the Spring DSL, you can specify your
HttpClientConfigurer
using the URI. For example:
<bean id="myHttpClientConfigurer"
class="my.https.HttpClientConfigurer">
</bean>
<to uri="https://myhostname.com:443/myURL?httpClientConfigurer=myHttpClientConfigurer"/>
As long as you implement the HttpClientConfigurer and configure your keystore and truststore as described above, it will work fine.
Using HTTPS to authenticate gotchas
An end user reported that he had problem with authenticating with HTTPS.
The problem was eventually resolved by providing a custom configured
org.apache.http.protocol.HttpContext
:
-
1. Create a (Spring) factory for HttpContexts:
public class HttpContextFactory {
private String httpHost = "localhost";
private String httpPort = 9001;
private BasicHttpContext httpContext = new BasicHttpContext();
private BasicAuthCache authCache = new BasicAuthCache();
private BasicScheme basicAuth = new BasicScheme();
public HttpContext getObject() {
authCache.put(new HttpHost(httpHost, httpPort), basicAuth);
httpContext.setAttribute(ClientContext.AUTH_CACHE, authCache);
return httpContext;
}
// getter and setter
}
-
2. Declare an HttpContext in the Spring application context file:
<bean id="myHttpContext" factory-bean="httpContextFactory" factory-method="getObject"/>
-
3. Reference the context in the http URL:
<to uri="https://myhostname.com:443/myURL?httpContext=myHttpContext"/>
Using different SSLContextParameters
The HTTP component only support one instance of
org.apache.camel.support.jsse.SSLContextParameters
per component. If you
need to use 2 or more different instances, then you need to setup
multiple HTTP components as shown below. Where we have
2 components, each using their own instance of sslContextParameters
property.
<bean id="http-foo" class="org.apache.camel.component.http.HttpComponent">
<property name="sslContextParameters" ref="sslContextParams1"/>
<property name="x509HostnameVerifier" ref="hostnameVerifier"/>
</bean>
<bean id="http-bar" class="org.apache.camel.component.http.HttpComponent">
<property name="sslContextParameters" ref="sslContextParams2"/>
<property name="x509HostnameVerifier" ref="hostnameVerifier"/>
</bean>