camel-https-kafka-connector sink configuration

camel.sink.path.httpUri

The url of the HTTP endpoint to call.

true

HIGH

camel.sink.endpoint.disableStreamCache

Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. If you use Servlet to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. The http producer will by default cache the response body stream. If setting this option to true, then the producers will not cache the response body stream but use the response stream as-is as the message body.

false

MEDIUM

camel.sink.endpoint.headerFilterStrategy

To use a custom HeaderFilterStrategy to filter header to and from Camel message.

false

MEDIUM

camel.sink.endpoint.httpBinding

To use a custom HttpBinding to control the mapping between Camel message and HttpClient.

false

MEDIUM

camel.sink.endpoint.bridgeEndpoint

If the option is true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint’s URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back.

false

MEDIUM

camel.sink.endpoint.chunked

If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response

false

MEDIUM

camel.sink.endpoint.clearExpiredCookies

Whether to clear expired cookies before sending the HTTP request. This ensures the cookies store does not keep growing by adding new cookies which is newer removed when they are expired. If the component has disabled cookie management then this option is disabled too.

false

MEDIUM

camel.sink.endpoint.connectionClose

Specifies whether a Connection Close header must be added to HTTP Request. By default connectionClose is false.

false

MEDIUM

camel.sink.endpoint.copyHeaders

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).

false

MEDIUM

camel.sink.endpoint.customHostHeader

To use custom host header for producer. When not set in query will be ignored. When set will override host header derived from url.

false

MEDIUM

camel.sink.endpoint.httpMethod

Configure the HTTP method to use. The HttpMethod header cannot override this option if set. One of: [GET] [POST] [PUT] [DELETE] [HEAD] [OPTIONS] [TRACE] [PATCH]

false

MEDIUM

camel.sink.endpoint.ignoreResponseBody

If this option is true, The http producer won’t read response body and cache the input stream

false

MEDIUM

camel.sink.endpoint.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

MEDIUM

camel.sink.endpoint.preserveHostHeader

If the option is true, HttpProducer will set the Host header to the value contained in the current exchange Host header, useful in reverse proxy applications where you want the Host header received by the downstream server to reflect the URL called by the upstream client, this allows applications which use the Host header to generate accurate URL’s for a proxied service

false

MEDIUM

camel.sink.endpoint.throwExceptionOnFailure

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.

false

MEDIUM

camel.sink.endpoint.transferException

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. 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. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.

false

MEDIUM

camel.sink.endpoint.cookieHandler

Configure a cookie handler to maintain a HTTP session

false

MEDIUM

camel.sink.endpoint.cookieStore

To use a custom CookieStore. By default the BasicCookieStore is used which is an in-memory only cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn’t be stored as we are just bridging (eg acting as a proxy). If a cookieHandler is set then the cookie store is also forced to be a noop cookie store as cookie handling is then performed by the cookieHandler.

false

MEDIUM

camel.sink.endpoint.deleteWithBody

Whether the HTTP DELETE should include the message body or not. By default HTTP DELETE do not include any HTTP body. However in some rare cases users may need to be able to include the message body.

false

MEDIUM

camel.sink.endpoint.getWithBody

Whether the HTTP GET should include the message body or not. By default HTTP GET do not include any HTTP body. However in some rare cases users may need to be able to include the message body.

false

MEDIUM

camel.sink.endpoint.okStatusCodeRange

The status codes which are considered a success response. The values are inclusive. Multiple ranges can be defined, separated by comma, e.g. 200-204,209,301-304. Each range must be a single number or from-to with the dash included.

false

MEDIUM

camel.sink.endpoint.skipRequestHeaders

Whether to skip mapping all the Camel headers as HTTP request headers. If there are no data from Camel headers needed to be included in the HTTP request then this can avoid parsing overhead with many object allocations for the JVM garbage collector.

false

MEDIUM

camel.sink.endpoint.skipResponseHeaders

Whether to skip mapping all the HTTP response headers to Camel headers. If there are no data needed from HTTP headers then this can avoid parsing overhead with many object allocations for the JVM garbage collector.

false

MEDIUM

camel.sink.endpoint.clientBuilder

Provide access to the http client request parameters used on new RequestConfig instances used by producers or consumers of this endpoint.

false

MEDIUM

camel.sink.endpoint.clientConnectionManager

To use a custom HttpClientConnectionManager to manage connections

false

MEDIUM

camel.sink.endpoint.connectionsPerRoute

The maximum number of connections per route.

false

MEDIUM

camel.sink.endpoint.httpClient

Sets a custom HttpClient to be used by the producer

false

MEDIUM

camel.sink.endpoint.httpClientConfigurer

Register a custom configuration strategy for new HttpClient instances created by producers or consumers such as to configure authentication mechanisms etc.

false

MEDIUM

camel.sink.endpoint.httpClientOptions

To configure the HttpClient using the key/values from the Map.

false

MEDIUM

camel.sink.endpoint.httpContext

To use a custom HttpContext instance

false

MEDIUM

camel.sink.endpoint.maxTotalConnections

The maximum number of connections.

false

MEDIUM

camel.sink.endpoint.useSystemProperties

To use System Properties as fallback for configuration

false

MEDIUM

camel.sink.endpoint.proxyAuthDomain

Proxy authentication domain to use with NTML

false

MEDIUM

camel.sink.endpoint.proxyAuthHost

Proxy authentication host

false

MEDIUM

camel.sink.endpoint.proxyAuthMethod

Proxy authentication method to use One of: [Basic] [Digest] [NTLM]

false

MEDIUM

camel.sink.endpoint.proxyAuthNtHost

Proxy authentication domain (workstation name) to use with NTML

false

MEDIUM

camel.sink.endpoint.proxyAuthPassword

Proxy authentication password

false

MEDIUM

camel.sink.endpoint.proxyAuthPort

Proxy authentication port

false

MEDIUM

camel.sink.endpoint.proxyAuthScheme

Proxy authentication scheme to use One of: [http] [https]

false

MEDIUM

camel.sink.endpoint.proxyAuthUsername

Proxy authentication username

false

MEDIUM

camel.sink.endpoint.proxyHost

Proxy hostname to use

false

MEDIUM

camel.sink.endpoint.proxyPort

Proxy port to use

false

MEDIUM

camel.sink.endpoint.authDomain

Authentication domain to use with NTML

false

MEDIUM

camel.sink.endpoint.authenticationPreemptive

If this option is true, camel-http sends preemptive basic authentication to the server.

false

MEDIUM

camel.sink.endpoint.authHost

Authentication host to use with NTML

false

MEDIUM

camel.sink.endpoint.authMethod

Authentication methods allowed to use as a comma separated list of values Basic, Digest or NTLM.

false

MEDIUM

camel.sink.endpoint.authMethodPriority

Which authentication method to prioritize to use, either as Basic, Digest or NTLM. One of: [Basic] [Digest] [NTLM]

false

MEDIUM

camel.sink.endpoint.authPassword

Authentication password

false

MEDIUM

camel.sink.endpoint.authUsername

Authentication username

false

MEDIUM

camel.sink.endpoint.sslContextParameters

To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.util.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need.

false

MEDIUM

camel.sink.endpoint.x509HostnameVerifier

To use a custom X509HostnameVerifier such as DefaultHostnameVerifier or NoopHostnameVerifier

false

MEDIUM

camel.component.https.cookieStore

To use a custom org.apache.http.client.CookieStore. By default the org.apache.http.impl.client.BasicCookieStore is used which is an in-memory only cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn’t be stored as we are just bridging (eg acting as a proxy).

false

MEDIUM

camel.component.https.copyHeaders

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).

false

MEDIUM

camel.component.https.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

MEDIUM

camel.component.https.responsePayloadStreaming Threshold

This threshold in bytes controls whether the response payload should be stored in memory as a byte array or be streaming based. Set this to -1 to always use streaming mode.

false

MEDIUM

camel.component.https.skipRequestHeaders

Whether to skip mapping all the Camel headers as HTTP request headers. If there are no data from Camel headers needed to be included in the HTTP request then this can avoid parsing overhead with many object allocations for the JVM garbage collector.

false

MEDIUM

camel.component.https.skipResponseHeaders

Whether to skip mapping all the HTTP response headers to Camel headers. If there are no data needed from HTTP headers then this can avoid parsing overhead with many object allocations for the JVM garbage collector.

false

MEDIUM

camel.component.https.allowJavaSerializedObject

Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.

false

MEDIUM

camel.component.https.authCachingDisabled

Disables authentication scheme caching

false

MEDIUM

camel.component.https.automaticRetriesDisabled

Disables automatic request recovery and re-execution

false

MEDIUM

camel.component.https.autowiredEnabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

false

MEDIUM

camel.component.https.clientConnectionManager

To use a custom and shared HttpClientConnectionManager to manage connections. If this has been configured then this is always used for all endpoints created by this component.

false

MEDIUM

camel.component.https.connectionsPerRoute

The maximum number of connections per route.

false

MEDIUM

camel.component.https.connectionStateDisabled

Disables connection state tracking

false

MEDIUM

camel.component.https.connectionTimeToLive

The time for connection to live, the time unit is millisecond, the default value is always keep alive.

false

MEDIUM

camel.component.https.contentCompressionDisabled

Disables automatic content decompression

false

MEDIUM

camel.component.https.cookieManagementDisabled

Disables state (cookie) management

false

MEDIUM

camel.component.https.defaultUserAgentDisabled

Disables the default user agent set by this builder if none has been provided by the user

false

MEDIUM

camel.component.https.httpBinding

To use a custom HttpBinding to control the mapping between Camel message and HttpClient.

false

MEDIUM

camel.component.https.httpClientConfigurer

To use the custom HttpClientConfigurer to perform configuration of the HttpClient that will be used.

false

MEDIUM

camel.component.https.httpConfiguration

To use the shared HttpConfiguration as base configuration.

false

MEDIUM

camel.component.https.httpContext

To use a custom org.apache.http.protocol.HttpContext when executing requests.

false

MEDIUM

camel.component.https.maxTotalConnections

The maximum number of connections.

false

MEDIUM

camel.component.https.redirectHandlingDisabled

Disables automatic redirect handling

false

MEDIUM

camel.component.https.headerFilterStrategy

To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.

false

MEDIUM

camel.component.https.proxyAuthDomain

Proxy authentication domain to use

false

MEDIUM

camel.component.https.proxyAuthHost

Proxy authentication host

false

MEDIUM

camel.component.https.proxyAuthMethod

Proxy authentication method to use One of: [Basic] [Digest] [NTLM]

false

MEDIUM

camel.component.https.proxyAuthNtHost

Proxy authentication domain (workstation name) to use with NTML

false

MEDIUM

camel.component.https.proxyAuthPassword

Proxy authentication password

false

MEDIUM

camel.component.https.proxyAuthPort

Proxy authentication port

false

MEDIUM

camel.component.https.proxyAuthUsername

Proxy authentication username

false

MEDIUM

camel.component.https.sslContextParameters

To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.support.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need.

false

MEDIUM

camel.component.https.useGlobalSslContext Parameters

Enable usage of global SSL context parameters.

false

MEDIUM

camel.component.https.x509HostnameVerifier

To use a custom X509HostnameVerifier such as DefaultHostnameVerifier or NoopHostnameVerifier.

false

MEDIUM

camel.component.https.connectionRequestTimeout

The timeout in milliseconds used when requesting a connection from the connection manager. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default).

false

MEDIUM

camel.component.https.connectTimeout

Determines the timeout in milliseconds until a connection is established. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default).

false

MEDIUM

camel.component.https.socketTimeout

Defines the socket timeout in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default).

false

MEDIUM