Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the asciidoc in the repository: https://github.com/apache/camel/blob/master/README.md https://github.com/apache/camel/blob/master/components/readme.adoc
If set to
Reference to an
Reference to an
On the consumer-side, all options of the Servlet component are supported.
On the producer-side the following headers of the Http component are supported.
The HTTP content type. Is set on both the
The HTTP content encoding. Is set on both the
The HTTP method to execute. One of
Overrides the query part of the endpoint URI or the the query part of
Overrides the default endpoint URI if the
The HTTP response code from URL fetch service responses.
On the consumer-side all headers of the Servlet component component are supported.
On the producer side the
in message body is converted to a
out message body is made available as
InputStream. If the reponse size exceeds 1 megabyte a ResponseTooLargeException is thrown by the URL fetch service (see quotas and limits).
For receiving messages via the
ghttp component, a
CamelHttpTransportServlet must be configured and mapped in the application's
web.xml. For example, to handle requests targeted at
http://localhost/camel/* (when using a local development server) the following servlet mapping must be defined:
Endpoint URI path definitions are relative to this servlet mapping e.g. the route
processes requests targeted at
http://<appname>.appspot.com/camel/greeting. In this example, the request body is ignored and the response body is set to
Hello. Requests targeted at
http://<appname>.appspot.com/camel/greeting/* are not processed by default. This requires setting the option
For sending resquests to external HTTP services the
ghttp component uses the URL fetch service. For example, the Camel homepage can the retrieved with the following endpoint definition on the producer-side.
The HTTP method used depends on the
Exchange.HTTP_METHOD message header or on the presence of an in-message body (
POST otherwise). Retrieving the Camel homepage via a GAE application is as simple as
GET request to
http://<appname>.appspot.com/camel/home returns the Camel homepage. HTTPS-based communication with external services can be enabled with the
Maven users will need to add the following dependency to their