...
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Name | Type | Description |
|---|
CamelHttpMethod
| String
| Allow to control what HTTP method to use such as GET, POST, TRACE etc. The type can also be a org.jboss.netty.handler.codec.http.HttpMethod instance. | CamelHttpQuery
| String
| Allows to provide URI query parameters as a String value that overrides the endpoint configuration. Separate multiple parameters using the & sign. For example: foo=bar&beer=yes. | CamelHttpPath
| String
| Camel 2.13.1/2.12.4: Allows to provide URI context-path and query parameters as a String value that overrides the endpoint configuration. This allows to reuse the same producer for calling same remote http server, but using a dynamic context-path and query parameters. | Content-Type
| String
| To set the content-type of the HTTP body. For example: text/plain; charset="UTF-8". | CamelHttpResponseCode | int | Allows to set the HTTP Status code to use. By default 200 is used for success, and 500 for failure. |
|
The following headers is provided as meta-data when a route starts from an Netty HTTP endpoint:
...
This component uses the org.apache.camel.component.netty.http.NettyHttpMessage as the message implementation on the Exchange. This allows end users to get access to the original Netty request/response instances if needed, as shown below:. Mind that the original response may not be accessible at all times.
| Code Block |
|---|
org.jboss.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
|
...
