NameOption | Default Value | Description |
|---|
bridgeEndpoint
| false
| Camel 2.1: 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 throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back. Camel 2.3: If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the Content-Encoding is gzip. Consider setting disableStreamCache=true to optimize when bridging. |
chunked
| true
| Camel 2.2: If this option is false Jetty Servlet will disable the HTTP streaming and set the Content-Length header on the response |
continuationTimeout
| null
| Camel 2.6: Allows to set a timeout in milliseconds when using Jetty as consumer (server). By default Jetty uses 30000. You can use a value of <= 0 to never expire. If a timeout occurs then the request will be expired and Jetty will return back an HTTP error 503 to the client. This option is only in use when using Jetty with the Asynchronous Routing Engine. |
disableStreamCache
| false
| Camel 2.3: Determines whether or not the raw input stream from Jetty 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 Jetty 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 Jetty 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.
|
enableCORS
| false
| Camel 2.15: if the option is true, Jetty server will setup the CrossOriginFilter which supports the CORS out of box. |
enableJmx
| false
| Camel 2.3: If this option is true, Jetty JMX support will be enabled for this endpoint. See Jetty JMX support for more details. |
enablemulti-partFilter
| true
| Camel 2.5: Whether Jetty org.eclipse.jetty.servlets.multi-partFilter is enabled or not. Set this option to false when bridging endpoints, to ensure multi-part requests is proxied/bridged as well. |
filterInit.xxx
| null
| Camel 2.17: Configuration for the InitParameters of filter. For example, setting filterInit.parameter=value the parameter could be used when calling the filter init() method. |
filtersRef
| null
| Camel 2.9: Allows using a custom filters which is putted into a list and can be find in the Registry |
handlers
| null
| Specifies a comma-delimited set of org.mortbay.jetty.Handler instances in your Registry (such as your Spring ApplicationContext). These handlers are added to the Jetty servlet Servlet context (for example, to add security). Note: you can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. |
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 HttpJettyEndpoint. |
httpBindingRef
| null
| Reference to an org.apache.camel.component.http.HttpBinding in the Registry. HttpBinding can be used to customize how a response should be written for the consumer. |
httpClient.xxx
| null
| Configuration of Jetty's HttpClient. For example, setting httpClient.idleTimeout=30000 sets the idle timeout to 30 seconds. And httpClient.timeout=30000 sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. |
httpClient
| null
| To use a shared org.eclipse.jetty.client.HttpClient for all producers created by this endpoint. This option should only be used in special circumstances. |
httpClientMinThreads
| null
| Camel 2.11: Producer only: To set a value for minimum number of threads in HttpClient thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to min 8 threads used in Jetty's thread pool. |
httpClientMaxThreads
| null
| Camel 2.11: Producer only: To set a value for maximum number of threads in HttpClient thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to max 16 threads used in Jetty's thread pool. |
httpMethodRestrict
| null
| Camel 2.11: Consumer only: Used to only allow consuming if the HttpMethod matches, such as GET/POST/PUT etc. From Camel 2.15: multiple methods can be specified separated by comma. |
jettyHttpBindingRef
| null
| Camel 2.6.0+: Reference to an org.apache.camel.component.jetty.JettyHttpBinding in the Registry. JettyHttpBinding can be used to customize how a response should be written for the producer. |
matchOnUriPrefix
| false
| Whether or not the CamelServlet should try to find a target consumer by matching the URI prefix if no exact match is found. See here How do I let Jetty match wildcards. |
multi-partFilterRef
| null
| Camel 2.6: Allows using a custom multi-part filter. Note: setting multi-partFilterRef forces the value of enablemulti-partFilter to true. |
okStatusCodeRange
| 200-299
| Camel 2.16: Producer only 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. |
optionsEnabled
| false
| Camel 2.17: Specifies whether to enable HTTP OPTIONS for this Jetty consumer. By default OPTIONS is turned off. |
proxyHost
| null
| Camel 2.11: Producer only The HTTP proxy Host URL which will be used by Jetty client. |
proxyPort
| null
| Camel 2.11: Producer only The HTTP proxy port which will be used by Jetty client. |
responseBufferSize
| null
| Camel 2.12: To use a custom buffer size on the javax.servlet.ServletResponse. |
sendDateHeader
| false
| Camel 2.14: if the option is true, jetty server will send the date header to the client which sends the request. Note: please make sure there is ensure that there are no any other camel-jetty endpoint is endpoints that share the same port, otherwise this option may not work as expected. |
sendServerVersion
| true
| Camel 2.13: if the option is true, jetty will send the server header with the jetty version information to the client which sends the request. Note: please make sure there is ensure that there are no any other camel-jetty endpoint is endpoints that share the same port, otherwise this option may not work as expected. |
sessionSupport
| false
| Specifies whether to enable the session manager on the server side of Jetty. |
sslContextParameters
| null
| Camel 2.17: 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. |
sslContextParametersRef
| null
| Camel 2.8: Deprecated 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. |
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. |
traceEnabled
| false
| Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. |
transferException
| false
| 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. 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. |
urlRewrite
| null
| 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. |
useContinuation
| true
| Camel 2.6: Whether or not to use Jetty continuations for the Jetty Server. |
