[CONF] Apache Camel HTTP4
willem jiang edited the page: HTTP4 ... Name Default Value Description maxTotalConnections 200 The maximum number of connections. connectionsPerRoute 20 The maximum number of connections per route. cookieStore null Camel 2.11.2/2.12.0: 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 cookies shouldn't be stored as we are just bridging (eg acting as a proxy). httpClientConfigurer null Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. clientConnectionManager null To use a custom org.apache.http.conn.ClientConnectionManager. httpBinding null To use a custom org.apache.camel.component.http.HttpBinding. httpContext null Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Comment:
CAMEL-6786
Changes (1)
...
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. | | {{connectionTimeToLive}} | {{-1}} | *Camel 2.11.0:* The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
| {{authenticationPreemptive}} | {{false}} | *Camel 2.11.3/2.12.2:* If this option is true, camel-http4 sends preemptive basic authentication to the server. |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
cookieStore
null
Camel 2.11.2/2.12.0: 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 cookies shouldn't be stored as we are just bridging (eg acting as a proxy).
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility. 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. See further below for more details.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive.
authenticationPreemptive
false
Camel 2.11.3/2.12.2: If this option is true, camel-http4 sends preemptive basic authentication to the server.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
clearExpiredCookies
true
Camel 2.11.2/2.12.0: 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.
cookieStore
null
Camel 2.11.2/2.12.0: To use a
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Christian Mueller
Changes (2)
...
h3. How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
{info:title=Using the http PATCH method} The http PATCH method is supported starting with Camel 2.11.3 / 2.12.1. {info}
The HTTP4 component provides a way to set the HTTP request method by setting the message header. Here is an example:
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
cookieStore
null
Camel 2.11.2/2.12.0: 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 cookies shouldn't be stored as we are just bridging (eg acting as a proxy).
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility. 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. See further below for more details.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
clearExpiredCookies
true
Camel 2.11.2/2.12.0: 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.
cookieStore
null
Camel 2.11.2/2.12.0: 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 cookies shouldn't be stored as we are just bridging (eg acting as a proxy).
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (2)
...
| {{maxTotalConnections}} | {{200}} | The maximum number of connections. | | {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. |
| {{cookieStore}} | {{null}} | *Camel 2.11.2/2.12.0:* 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 cookies shouldnt be stored as we are just bridging (eg acting as a proxy). |
| {{httpClientConfigurer}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. | | {{clientConnectionManager}} | {{null}} | To use a custom {{org.apache.http.conn.ClientConnectionManager}}. |
...
| {{throwExceptionOnFailure}} | {{true}} | 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. | | {{bridgeEndpoint}} | {{false}} | If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. |
| {{clearExpiredCookies}} | {{true}} | *Camel 2.11.2/2.12.0:* 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. | | {{cookieStore}} | {{null}} | *Camel 2.11.2/2.12.0:* 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 cookies shouldnt be stored as we are just bridging (eg acting as a proxy). |
| {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. | | {{headerFilterStrategy}} | {{null}} | *Camel 2.10.4:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. |
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
cookieStore
null
Camel 2.11.2/2.12.0: 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 cookies shouldn't be stored as we are just bridging (eg acting as a proxy).
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (4)
...
| {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. | | {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. |
| {{sslContextParameters}} | {{null}} | *Camel 2.8:* To use a custom {{org.apache.camel.util.jsse.SSLContextParameters}}. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. *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. See further below for more details. |
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. | | {{connectionTimeToLive}} | {{-1}} | *Camel 2.11.0:* The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
...
| {{clientConnectionManager}} | {{null}} | To use a custom {{org.apache.http.conn.ClientConnectionManager}}. | | {{transferException}} | {{false}} | If enabled and an [Exchange] failed processing on the consumer side, and if the caused {{Exception}} was send back serialized in the response as a {{application/x-java-serialized-object}} content type (for example using [Jetty] or [Servlet] Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the {{HttpOperationFailedException}}. The caused exception is required to be serialized. |
| {{sslContextParametersRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry]. This reference overrides any configured SSLContextParameters at the component level. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. Use the {{sslContextParameters}} option instead. | | {{sslContextParameters}} | {{null}} | *Camel 2.11.1:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry]. This reference overrides any configured SSLContextParameters at the component level. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. |
| {{sslContextParametersRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry]. *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. See further below for more details. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. Use the {{sslContextParameters}} option instead. | | {{sslContextParameters}} | {{null}} | *Camel 2.11.1:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry]. *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. See further below for more details. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. |
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. | | {{urlRewrite}} | {{null}} | *Camel 2.11:* *Producer only* Refers to a custom {{org.apache.camel.component.http4.UrlRewrite}} which allows you to rewrite urls when you bridge/proxy endpoints. See more details at [UrlRewrite] and [How to use Camel as a HTTP proxy between a client and server]. |
...
to uri=https4://myhostname.com:443/myURL?httpContext=myHttpContext/ {code}
h5. Using different SSLContextParameters The [HTTP4] component only support one instance of {{org.apache.camel.util.jsse.SSLContextParameters}} per component. If you need to use 2 or more different instances, then you need to setup multiple [HTTP4] components as shown below. Where we have 2 components, each using their own instance of {{sslContextParameters}} property. {code:xml} bean id=http4-foo
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Christian Mueller
Changes (6)
...
| {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. | | {{headerFilterStrategy}} | {{null}} | *Camel 2.10.4:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. |
| {{httpBindingRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. Recommended to use Use the {{httpBinding}} option instead. |
| {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. |
| {{httpClientConfigurerRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. Recommended to use Use the {{httpClientConfigurer}} option instead. |
| {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. | | {{httpContextRef}} | {{null}} | *Camel 2.9.2:* Reference to a custom {{org.apache.http.protocol.HttpContext}} in the [Registry]. Recommended to use the {{httpContext}} option instead. |
| {{httpClientConfigurer}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. |
| {{httpContextRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* *Camel 2.9.2:* Reference to a custom {{org.apache.http.protocol.HttpContext}} in the [Registry]. Use the {{httpContext}} option instead. | | {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. |
| {{httpClient.XXX}} | {{null}} | Setting options on the [BasicHttpParams|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/BasicHttpParams.html]. For instance {{httpClient.soTimeout=5000}} will set the {{SO_TIMEOUT}} to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: [AuthParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/auth/params/AuthParamBean.html], [ClientParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/params/ClientParamBean.html], [ConnConnectionParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnConnectionParamBean.html], [ConnRouteParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnRouteParamBean.html], [CookieSpecParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/params/CookieSpecParamBean.html], [HttpConnectionParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpConnectionParamBean.html] and [HttpProtocolParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpProtocolParamBean.html] | | {{clientConnectionManager}} | {{null}} | To use a custom {{org.apache.http.conn.ClientConnectionManager}}. | | {{transferException}} | {{false}} | If enabled and an [Exchange] failed processing on the consumer side, and if the caused {{Exception}} was send back serialized in the response as a {{application/x-java-serialized-object}} content type (for example using [Jetty] or [Servlet] Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the {{HttpOperationFailedException}}. The caused exception is required to be serialized. |
| {{sslContextParametersRef}} | {{null}} | *Deprecated and will be removed in Camel 3.0:* *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. Use the {{sslContextParameters}} option instead. |
| {{sslContextParameters}} | {{null}} | *Camel 2.11.1:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry]. This reference overrides any configured SSLContextParameters at the component level. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. |
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (1)
...
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.
h4. Using HTTPS to authenticate gotchas An end user reported that he had problem with authenticating with HTTPS. The problem was eventually resolved when he discovered the HTTPS server did not return a HTTP code 401 Authorization Required. The solution was to set the following URI option: {{httpClient.authenticationPreemptive=true}}
h4. Setting up SSL for HTTP Client
h5. Using the JSSE Configuration Utility
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel 2.9.2: Reference to a custom org.apache.http.protocol.HttpContext in the Registry. Recommended to use the
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Christian Mueller
Changes (1)
...
As long as you implement the HttpClientConfigurer and configure your keystore and truststore as described above, it will work fine.
h5. 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: {code} 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 } {code} 2. Declare an HttpContext in the Spring application context file: {code} bean id=myHttpContext factory-bean=httpContextFactory factory-method=getObject/ {code} 3. Reference the context in the http4 URL: {code} to uri=https4://myhostname.com:443/myURL?httpContext=myHttpContext/ {code}
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Changes (1)
...
| {{sslContextParameters}} | {{null}} | *Camel 2.8:* To use a custom {{org.apache.camel.util.jsse.SSLContextParameters}}. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. | | {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
| {{connectionTimeToLive}} | {{-1}} | The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
The time for connection to live, the time unit is millisecond, the default value is always keep alive.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel 2.9.2: Reference to a custom
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Changes (1)
...
| {{sslContextParameters}} | {{null}} | *Camel 2.8:* To use a custom {{org.apache.camel.util.jsse.SSLContextParameters}}. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. | | {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
| {{connectionTimeToLive}} | {{-1}} | *Camel 2.11.0:* The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
connectionTimeToLive
-1
Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Changes (1)
...
In the sample above Camel will call the [http://newhost] despite the endpoint is configured with [http4://oldhost]. Where Constants is the class, {{org.apache.camel.component.http4.Constants}}.
If the http4 endpoint is working in bridge mode, it will ignore the message header of {{Exchange.HTTP_URI}}.
h3. Configuring URI Parameters
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel 2.9.2: Reference to a custom org.apache.http.protocol.HttpContext in the Registry. Recommended to use the httpContext option instead.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
httpClient.XXX
null
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference:
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Christian Mueller
Changes (2)
...
{code}
You can override the HTTP endpoint URI by adding a header with the key, {{HttpConstants.HTTP_URI}}, {{Exchange.HTTP_URI}}, on the message.
{code} from(direct:start)
.setHeader(HttpConstants.HTTP_URI, .setHeader(Exchange.HTTP_URI, constant(http://newhost))
.to(http4://oldhost);
{code} In the sample above Camel will call the [http://newhost] despite the endpoint is configured with [http4://oldhost].
...
{code} from(direct:start)
.to(http4://oldhost?order=123detail=short);
{code} Or options provided in a header: {code} from(direct:start)
.setHeader(Exchange.HTTP_QUERY, constant(order=123detail=short))
.to(http4://oldhost);
{code}
...
{code} from(direct:start)
.setHeader(Exchange.HTTP_METHOD, constant(org.apache.camel.component.http4.HttpMethods.POST))
.to(http4://www.google.com)
.to(mock:results);
{code}
...
{code} from(direct:start)
.to(http4://oldhost?proxyAuthHost=www.myproxy.comproxyAuthPort=80);
{code}
...
{code} from(timer://foo?fixedRate=truedelay=0period=1)
.to(http4://www.google.com)
.setHeader(FileComponent.HEADER_FILE_NAME, message.html)
.to(file:target/google);
{code}
...
{code:java} Exchange exchange = template.send(http4://www.google.com/search, new Processor() {
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(HttpProducer.QUERY, constant(hl=enq=activemq));
}
});
Message out = exchange.getOut();
int responseCode = out.getHeader(HttpProducer.HTTP_RESPONSE_CODE, Integer.class);
{code}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (2)
...
*Available as of Camel 2.3*
The *http4:* component provides HTTP based [endpoints|Endpoint] for consuming 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:
...
| {{sslContextParametersRef}} | {{null}} | *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. | | {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
| {{urlRewrite}} | {{null}} | *Camel 2.11:* *Producer only* Refers to a custom {{org.apache.camel.component.http4.UrlRewrite}} which allows you to rewrite urls when you bridge/proxy endpoints. See more details at [UrlRewrite] and [How to use Camel as a HTTP proxy between a client and server]. |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Christian Mueller
Changes (1)
...
| {{bridgeEndpoint}} | {{false}} | If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. | | {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. |
| {{headerFilterStrategy}} | {{null}} | *Camel 2.11:* 2.10.4:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. |
| {{httpBindingRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. Recommended to use the {{httpBinding}} option instead. | | {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. |
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.10.4: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (2)
...
{div}
h3. HttpComponent Options
{div:class=confluenceTableSmall} || Name || Default Value || Description || | {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. | | {{httpClientConfigurer}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpClientConfigurer}}. | | {{httpConnectionManager}} | {{null}} | To use a custom {{org.apache.commons.httpclient.HttpConnectionManager}}. | | {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. | | {{x509HostnameVerifier}} | {{null}} | *Camel 2.7:* To use a custom {{org.apache.http.conn.ssl.X509HostnameVerifier.}} | | {{sslContextParameters}}\\ | null\\ | *Camel 2.8:* To configure a custom SSL/TLS configuration options at the component level.nbsp; Seenbsp; [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility] for more details.\\ | {div}
h3. Message Headers
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpComponent Options
Name
Default Value
Description
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
sslContextParameters
null
Camel 2.8: To use a custom org.apache.camel.util.jsse.SSLContextParameters. See Using the JSSE Configuration Utility.
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
HttpEndpoint Options
Name
Default Value
Description
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
headerFilterStrategy
null
Camel 2.11: Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry.It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (8)
...
{info}
h3. HttpEndpoint HttpComponent Options
{div:class=confluenceTableSmall} || Name || Default Value || Description ||
| {{maxTotalConnections}} | {{200}} | The maximum number of connections. | | {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. | | {{httpClientConfigurer}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. | | {{clientConnectionManager}} | {{null}} | To use a custom {{org.apache.http.conn.ClientConnectionManager}}. | | {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. | | {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. | | {{sslContextParameters}} | {{null}} | *Camel 2.8:* To use a custom {{org.apache.camel.util.jsse.SSLContextParameters}}. See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. |
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
{div} h3. HttpEndpoint Options {div:class=confluenceTableSmall} || Name || Default Value || Description ||
| {{throwExceptionOnFailure}} | {{true}} | 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. | | {{bridgeEndpoint}} | {{false}} | If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. | | {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. |
| {{headerFilterStrategy}} | {{null}} | *Camel 2.11:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. |
| {{httpBindingRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. Recommended to use the {{httpBinding}} option instead. | | {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. |
...
| {{clientConnectionManager}} | {{null}} | To use a custom {{org.apache.http.conn.ClientConnectionManager}}. | | {{transferException}} | {{false}} | If enabled and an [Exchange] failed processing on the consumer side, and if the caused {{Exception}} was send back serialized in the response as a {{application/x-java-serialized-object}} content type (for example using [Jetty] or [Servlet] Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the {{HttpOperationFailedException}}. The caused exception is required to be serialized. |
| {{maxTotalConnections}} | {{200}} | The maximum number of connections. | | {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. |
| {{sslContextParametersRef}} | {{null}} | *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level.nbsp; See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility]. |
| {{headerFilterStrategy}}\\ | {{null}}\\ | *Camel 2.11:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.\\ |
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Comment:
CAMEL-5575
Changes (1)
...
| {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. | | {{sslContextParametersRef}}\\ | {{null}}\\ | *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level.nbsp; See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility].\\ |
| {{headerFilterStrategy}} \\| {{null}} \\ | *Camel 2.11:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. \\|
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel 2.9.2: Reference to a custom org.apache.http.protocol.HttpContext in the Registry. Recommended to use the httpContext option instead.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
httpClient.XXX
null
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
transferException
false
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or SERVLET Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Changes (0)
...
| {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. | | {{sslContextParametersRef}}\\ | {{null}}\\ | *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level.nbsp; See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility].\\ |
| {{headerFilterStrategy}}\\ | {{null}}\\ | *Camel 2.11:* Reference to a instance of {{org.apache.camel.spi.HeaderFilterStrategy}} in the [Registry].nbsp;It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.\\ |
{div}
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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, use the Jetty Component instead.
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
httpBinding
null
To use a custom org.apache.camel.component.http.HttpBinding.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
httpContext
null
Camel 2.9.2: To use a custom org.apache.http.protocol.HttpContext when executing requests.
httpContextRef
null
Camel 2.9.2: Reference to a custom org.apache.http.protocol.HttpContext in the Registry. Recommended to use the httpContext option instead.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
httpClient.XXX
null
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
transferException
false
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or SERVLET Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Glen Mazza
Comment:
proofreading
Changes (14)
...
{info:title=camel-http4 vs camel-jetty}
You can only produce to endpoints generated by the HTTP4 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|Jetty]
You can produce only to endpoints generated by the HTTP4 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, use the [Jetty Component|Jetty] instead.
{info}
...
| {{x509HostnameVerifier}} | {{BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. | | {{throwExceptionOnFailure}} | {{true}} | 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. |
| {{bridgeEndpoint}} | {{false}} | If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. |
| {{bridgeEndpoint}} | {{false}} | If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. |
| {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support read it twice, multiple reads, otherwise DefaultHttpBinding will set the request input stream directly into the message body. |
| {{httpBindingRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. Prefer Recommended to use the {{httpBinding}} option instead. |
| {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. |
| {{httpClientConfigurerRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. Prefer Recommended to use the {{httpClientConfigurer}} option instead. |
| {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. |
| {{httpContextRef}} | {{null}} | *Camel 2.9.2:* Reference to a custom {{org.apache.http.protocol.HttpContext}} in the [Registry]. Prefer Recommended to use the {{httpContext}} option instead. |
| {{httpClientConfigurer}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. | | {{httpClient.XXX}} | {{null}} | Setting options on the [BasicHttpParams|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/BasicHttpParams.html]. For instance {{httpClient.soTimeout=5000}} will set the {{SO_TIMEOUT}} to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: [AuthParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/auth/params/AuthParamBean.html], [ClientParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/params/ClientParamBean.html], [ConnConnectionParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnConnectionParamBean.html], [ConnRouteParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnRouteParamBean.html], [CookieSpecParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/params/CookieSpecParamBean.html], [HttpConnectionParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpConnectionParamBean.html] and [HttpProtocolParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpProtocolParamBean.html] |
...
h3. Calling using GET or POST
The following algorithm is used to determine if either
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (4)
...
| {{disableStreamCache}} | {{false}} | DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body. | | {{httpBindingRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. Prefer to use the {{httpBinding}} option. |
| {{httpBinding}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpBinding}} in the [Registry]. |
| {{httpBinding}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpBinding}}. |
| {{httpClientConfigurerRef}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. Prefer to use the {{httpClientConfigurer}} option. |
| {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. | | {{httpContextRef}} | {{null}} | *Camel 2.9.2:* Reference to a custom {{org.apache.http.protocol.HttpContext}} in the [Registry]. Prefer to use the {{httpContext}} option. |
| {{httpClientConfigurer}} | {{null}} | Reference to a {{org.apache.camel.component.http.HttpClientConfigurer}} in the [Registry]. | | {{httpClient.XXX}} | {{null}} | Setting options on the [BasicHttpParams|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/BasicHttpParams.html]. For instance {{httpClient.soTimeout=5000}} will set the {{SO_TIMEOUT}} to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: [AuthParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/auth/params/AuthParamBean.html], [ClientParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/params/ClientParamBean.html], [ConnConnectionParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnConnectionParamBean.html], [ConnRouteParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnRouteParamBean.html], [CookieSpecParamBean|http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/params/CookieSpecParamBean.html], [HttpConnectionParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpConnectionParamBean.html] and [HttpProtocolParamBean|http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpProtocolParamBean.html] |
...
| {{httpClientConfigurer}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpClientConfigurer}}. | | {{httpConnectionManager}} | {{null}} | To use a custom {{org.apache.commons.httpclient.HttpConnectionManager}}. |
| {{httpContext}} | {{null}} | *Camel 2.9.2:* To use a custom {{org.apache.http.protocol.HttpContext}} when executing requests. |
| {{x509HostnameVerifier}} | {{null}} | *Camel 2.7:* To use a custom {{org.apache.http.conn.ssl.X509HostnameVerifier.}} | | {{sslContextParameters}}\\ | null\\ | *Camel 2.8:* To configure a custom SSL/TLS configuration options at the component level.nbsp; Seenbsp; [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility] for more details.\\ |
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different
[CONF] Apache Camel HTTP4
HTTP4
Page edited by Claus Ibsen
Changes (7)
...
{div:class=confluenceTableSmall} || Name || Default Value || Description ||
| {{x509HostnameVerifier}} | {{org.apache.http.conn.ssl.BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
| {{throwExceptionOnFailure}} | {{true}} | 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. | | {{bridgeEndpoint}} | {{false}} | If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. |
...
{div:class=confluenceTableSmall} || Name || Default Value || Description ||
| {{authUsername}} | {{null}} | Username for authentication. |
| {{authPassword}} | {{null}} | Password for authentication. |
| {{authDomain}} | {{null}} | The domain name for authentication. |
| {{authHost}} | {{null}} | The host name authentication. |
| {{proxyAuthHost}} | {{null}} | The proxy host name | | {{proxyAuthPort}} | {{null}} | The proxy port number |
| {{proxyAuthScheme}} | {{null}} | The proxy scheme, will fallback and use the scheme from the endpoint if not configured. |
| {{proxyAuthUsername}} | {{null}} | Username for proxy authentication | | {{proxyAuthPassword}} | {{null}} | Password for proxy authentication |
...
So you can override the system properties with the endpoint options.
Notice in *Camel 2.8* there is also a {{http.proxyScheme}} property you can set to explicit configure the scheme to use.
h3. Configuring charset
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
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 throwExcpetionOnFailure to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Prefer to use the httpBinding option.
httpBinding
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry.
[CONF] Apache Camel HTTP4
HTTP4
Page edited by David Valeri
Changes (6)
...
{div:class=confluenceTableSmall} || Name || Default Value || Description ||
| {{x509HostnameVerifier}} | {{org.apache.http.conn.ssl.BrowserCompatHostnameVerifier}} | *Camel 2.7:* You can refer to a different {{org.apache.http.conn.ssl.X509HostnameVerifier}} instance in the [Registry] such as {{org.apache.http.conn.ssl.StrictHostnameVerifier}} or {{org.apache.http.conn.ssl.AllowAllHostnameVerifier}}. |
| {{throwExceptionOnFailure}} | {{true}} | 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. | | {{bridgeEndpoint}} | {{false}} | If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoints URI for request. You may also set the *throwExcpetionOnFailure* to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is gzip. |
...
| {{maxTotalConnections}} | {{200}} | The maximum number of connections. | | {{connectionsPerRoute}} | {{20}} | The maximum number of connections per route. |
| {{sslContextParametersRef}}\\ | {{null}}\\ | *Camel 2.8:* Reference to a {{org.apache.camel.util.jsse.SSLContextParameters}} in the [Registry].nbsp; This reference overrides any configured SSLContextParameters at the component level.nbsp; See [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility].\\ |
{div}
...
| {{httpClientConfigurer}} | {{null}} | To use a custom {{org.apache.camel.component.http.HttpClientConfigurer}}. | | {{httpConnectionManager}} | {{null}} | To use a custom {{org.apache.commons.httpclient.HttpConnectionManager}}. |
| {{x509HostnameVerifier}} | {{null}} | *Camel 2.7:* To use a custom {{org.apache.http.conn.ssl.X509HostnameVerifier.}} |
| {{sslContextParameters}}\\ | null\\ | *Camel 2.8:* To configure a custom SSL/TLS configuration options at the component level.nbsp; Seenbsp; [Using the JSSE Configuration Utility|#Using the JSSE Configuration Utility] for more details.\\ |
{div}
...
- 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.
{tip:title=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.
...
h4. Setting up SSL for HTTP Client
h5. Using the JSSE Configuration Utility As of Camel 2.8, the HTTP4 component supports SSL/TLS configuration through the [Camel JSSE Configuration Utility|CAMEL:Camel Configuration Utilities].nbsp; This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.nbsp; The following examples demonstrate how to use the utility with the HTTP4 component. h6. Programmatic configuration of the component {code} 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(http4, HttpComponent.class); httpComponent.setSslContextParameters(scp); {code} h6. Spring DSL based configuration of endpoint {code:xml} ... camel:sslContextParameters id=sslContextParameters camel:keyManagers keyPassword=keyPassword camel:keyStore resource=/users/home/server/keystore.jks password=keystorePassword/ /camel:keyManagers /camel:sslContextParameters... ... to uri=https4://127.0.0.1/mail/?sslContextParametersRef=sslContextParameters/... {code} h5. Configuring Apache HTTP Client Directly
Basically camel-http4 component is built on the top of [Apache HTTP client|http://hc.apache.org/]. Please refer to [SSL/TLS customization|http://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html#d4e537] for details or have a look into the
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Comment:
CAMEL-3780
Changes (2)
...
h4. Setting Basic Authentication and Proxy
*Before Camel 2.8.0*
{div:class=confluenceTableSmall} || Name || Default Value || Description ||
...
| {{proxyNtHost}} | {{null}} | The proxy Nt host name | {div}
*Since Camel 2.8.0* {div:class=confluenceTableSmall} || Name || Default Value || Description || | {{authUsername}} | {{null}} | Username for authentication. | | {{authPassword}} | {{null}} | Password for authentication. | | {{authDomain}} | {{null}} | The domain name for authentication. | | {{authHost}} | {{null}} | The host name authentication. | | {{proxyAuthHost}} | {{null}} | The proxy host name | | {{proxyAuthPort}} | {{null}} | The proxy port number | | {{proxyAuthUsername}} | {{null}} | Username for proxy authentication | | {{proxyAuthPassword}} | {{null}} | Password for proxy authentication | | {{proxyAuthDomain}} | {{null}} | The proxy domain name | | {{proxyAuthNtHost}} | {{null}} | The proxy Nt host name | {div}
h3. HttpComponent Options
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
org.apache.http.conn.ssl.BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
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 throwExcpetionOnFailure to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Prefer to use the httpBinding option.
httpBinding
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Prefer to use the httpClientConfigurer option.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
httpClient.XXX
null
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
transferException
false
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or SERVLET Camel components). On the
[CONF] Apache Camel HTTP4
HTTP4
Page edited by willem jiang
Changes (2)
...
{code} from(direct:start)
.to(http4://oldhost?proxyAuthHost=www.myproxy.comproxyAuthPort=80);
{code}
There is also support for proxy authentication via the {{proxyAuthUsername}} and {{proxyAuthPassword}} options.
h4. Using proxy settings outside of URI
...
Full Content
HTTP4 Component
Available as of Camel 2.3
The http4: component provides HTTP based endpoints for consuming 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
groupIdorg.apache.camel/groupId
artifactIdcamel-http4/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x.
URI format
http4:hostname[:port][/resourceUri][?options]
Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format, ?option=valueoption=value...
camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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
HttpEndpoint Options
Name
Default Value
Description
x509HostnameVerifier
org.apache.http.conn.ssl.BrowserCompatHostnameVerifier
Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier.
throwExceptionOnFailure
true
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.
bridgeEndpoint
false
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 throwExcpetionOnFailure to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
disableStreamCache
false
DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body.
httpBindingRef
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Prefer to use the httpBinding option.
httpBinding
null
Reference to a org.apache.camel.component.http.HttpBinding in the Registry.
httpClientConfigurerRef
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Prefer to use the httpClientConfigurer option.
httpClientConfigurer
null
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
httpClient.XXX
null
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean
clientConnectionManager
null
To use a custom org.apache.http.conn.ClientConnectionManager.
transferException
false
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or SERVLET Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized.
maxTotalConnections
200
The maximum number of connections.
connectionsPerRoute
20
The maximum number of connections per route.
The following authentication options can also be set on the HttpEndpoint:
Setting Basic Authentication and Proxy
Before Camel 2.8.0
Name
Default Value
Description
username
null
Username for authentication.
password
null
Password for authentication.
domain
null
The domain name for authentication.
host
null
The host name authentication.
proxyHost
null
The proxy host name
proxyPort
null
The proxy port number
[CONF] Apache Camel HTTP4
HTTP4 Page added by Christian Mueller HTTP4 Component Available as of Camel 2.3 The http4: component provides HTTP based endpoints for consuming 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 groupIdorg.apache.camel/groupId artifactIdcamel-http4/artifactId versionx.x.x/version !-- use the same version as your Camel core version -- /dependency camel-http4 vs camel-httpCamel-http4 uses HttpClient 4.x while camel-http uses HttpClient 3.x. URI format http4:hostname[:port][/resourceUri][?options] Will by default use port 80 for HTTP and 443 for HTTPS. You can append query options to the URI in the following format, ?option=valueoption=value... camel-http4 vs camel-jettyYou can only produce to endpoints generated by the HTTP4 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 HttpEndpoint Options Name Default Value Description x509HostnameVerifier org.apache.http.conn.ssl.BrowserCompatHostnameVerifier Camel 2.7: You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier. throwExceptionOnFailure true 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. bridgeEndpoint false 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 throwExcpetionOnFailure to be false to let the HttpProducer send all the fault response back. If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". disableStreamCache false DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body. httpBindingRef null Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Prefer to use the httpBinding option. httpBinding null Reference to a org.apache.camel.component.http.HttpBinding in the Registry. httpClientConfigurerRef null Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Prefer to use the httpClientConfigurer option. httpClientConfigurer null Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. httpClient.XXX null Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean clientConnectionManager null To use a custom org.apache.http.conn.ClientConnectionManager. transferException false If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or SERVLET Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized. maxTotalConnections 200 The maximum number of connections. connectionsPerRoute 20 The maximum number of connections per route. The following authentication options can also be set on the HttpEndpoint: Setting Basic Authentication and Proxy Name Default Value Description username null Username for authentication. password null Password for authentication. domain null The domain name for authentication. host null The host name authentication. proxyHost null The proxy host name proxyPort null The proxy port number proxyUsername null Username for proxy authentication proxyPassword null Password for proxy authentication proxyDomain null The proxy domain name proxyNtHost null The proxy Nt host name HttpComponent Options Name Default Value Description httpBinding null To use a custom org.apache.camel.component.http.HttpBinding. httpClientConfigurer null To use a custom org.apache.camel.component.http.HttpClientConfigurer. httpConnectionManager null To use a custom
