...
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 the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set throwExceptionOnFailure=false to let ensure all responses are propagated back to the HttpProducer send all the fault response back. From Camel 2.3: If the option is true , when true the HttpProducer and CamelServlet will skip the gzip processing when content-encoding=gzip . | disableStreamCache
| false
| When false the DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body which allows it to be read more than once. When true the if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body. From Camel 2.17: this options is now also support by the producer to allow using the response stream directly instead of stream caching as by default. | httpBindingRef
| null
| Deprecated and removed in Camel 2.17: Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Use the httpBinding option instead.
| httpBinding
| null
| From Camel 2.3: reference to a org.apache.camel.component.http.HttpBinding in the Registry. | httpClientConfigurerRef
| null
| Deprecated and removed in Camel 2.17: Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Use the httpClientConfigurer option instead.
| httpClientConfigurer
| null
| From Camel 2.3: reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. | httpClient.XXX
| null
| Setting options on the HttpClientParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. | clientConnectionManager
| null
| To use a custom org.apache.http.conn.ClientConnectionManager . | transferException
| false
| From Camel 2.6: 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 will be serialized. | headerFilterStrategy
| null
| From 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 . | urlRewrite
| null
| From Camel 2.11: Producer only! Refers to a custom org.apache.camel.component.http.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. | eagerCheckContentAvailable
| false
| From Camel 2.15.3/2.16: Consumer only! Whether to eager check whether the HTTP requests has content when content-length=0 or is not present. This can be turned on in case option should be set to true for those HTTP clients that do not send streamed data. | copyHeaders
| true
| From Camel 2.16: if this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Setting this to false , allows to only include the headers from the HTTP response (not propagating IN headers). | okStatusCodeRange
| 200-299
| From Camel 2.16: the range of HTTP status codes for which a response is considered a success response. The values are inclusive. The range must be defined as from-to with the dash included. | ignoreResponseBody
| false
| From Camel 2.16: if this option is when true , the HttpProducer won't will not read the response body and nor cache the input stream. | cookieHandler
| null
| From Camel: 2.19: configure a cookie handler to maintain a HTTP session |
|
...
The HTTP component uses convention over configuration which means that if you have not explicit set a authMethodPriority
then it will fallback and use the select(ed) authMethod
as priority as well. So if you use authMethod.Basic
then the auhtMethodPriority
will be Basic
only.
Info |
---|
Note: camel-http is based on HttpClient v3.x and as such has only limited support for what is known as NTLMv1, the early version of the NTLM protocol. It does not support NTLMv2 at all. camel-http4 has support for NTLMv2. |
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 . | httpConfiguration
| null
| To use a custom org.apache.camel.component.http.HttpConfiguration. | allowJavaSerializedObject | false | Camel 2.16.1/2.15.5: Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object . If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. |
|
...
Using Pre-Emptive Authentication
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 If an HTTP server should fail to respond correctly with an expected 401 Authorization Required
response for a failed authentication attempt a client can instead use preemptive authentication by specifying the URI option: httpClient.authenticationPreemptive=true
.
Accepting Self-Signed Certificates From Remote Server
...