The Jetty component only supports consumer endpoints. Therefore a Jetty endpoint URI should be used only as the input for a Apache Camel route. To issue HTTP requests against other HTTP endpoints, use the HTTP Component.

Jetty is stream based, which means the input it receives is submitted to Camel as a stream. That means you will only be able to read the content of the stream once. If you find a situation where the message body appears to be empty or you need to access the data multiple times (eg: doing multicasting, or redelivery error handling) you should use Stream Caching or convert the message body to a String which is safe to be re-read multiple times.

Table 5.6 lists the options for a Jetty endpoint.

Apache Camel uses the same message headers as the HTTP component. It also uses the Exchange.HTTP_CHUNKED header to turn on or turn off the chuncked encoding on the consumer.

Apache Camel also populates all request.parameter and request.headers. For example, given a client request with the URL http://myserver/myserver?orderid=123, the exchange will contain a header named orderid with the value 123.