...
Name | Default Value | Description |
---|---|---|
|
| The maximum number of connections. |
|
| The maximum number of connections per route. |
|
| Camel 2.11.2/2.12.0: To use a custom |
|
| Reference to a |
|
| To use a custom |
|
| To use a custom |
|
| Camel 2.9.2: To use a custom |
|
| Camel 2.8: To use a custom |
|
| Camel 2.7: You can refer to a different |
|
| Camel 2.11.0: The time for connection to live, the time unit is millisecond, the default value is always keep alive. |
|
| Camel 2.16.1/2.15.5: Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. |
HttpEndpoint Options
Name | Default Value | Description |
---|---|---|
|
| Option to disable throwing the |
|
| 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". |
|
| 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. |
|
| Camel 2.11.2/2.12.0: To use a custom |
|
| 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. 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. |
|
| Camel 2.10.4: Reference to a instance of |
|
| Deprecated and will be removed in Camel 3.0: Reference to a |
|
| To use a custom |
|
|
|
|
| Reference to a |
|
|
|
|
| Camel 2.9.2: To use a custom |
|
| Setting options on the BasicHttpParams. For instance Since Camel 2.13.0: httpClient is changed to configure the HttpClientBuilder and RequestConfig.Builder, please check out API document for a complete reference. E.g. since this version use |
|
| To use a custom |
|
| If enabled and an Exchange failed processing on the consumer side, and if the caused |
|
|
|
|
| Camel 2.11.1: Reference to a |
|
| Camel 2.7: You can refer to a different |
|
| Camel 2.11: Producer only Refers to a custom |
|
| Camel 2.14: The maximum number of total connections that the connection manager has. If this option is not set, camel will use the component's setting instead. |
|
| Camel 2.14: The maximum number of connections per route. If this option is not set, camel will use the component's setting instead. |
|
| Camel 2.11.3/2.12.2: If this option is true, camel-http4 sends preemptive basic authentication to the server. |
|
| Camel 2.16: Consumer only Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data. |
|
| 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 |
| Camel 2.16: The status codes which is considered a success response. The values are inclusive. The range must be defined as from-to with the dash included. |
ignoreResponseBody |
| Camel 2.16: If this option is true, The http producer won't read response body and cache the input stream. |
The following authentication options can also be set on the HttpEndpoint:
...