...
Name | POST_TO_URI | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | This property makes the request URL that is sent from WSO2 Enterprise Integrator(WSO2 EI) the ESB profile a complete URL. When set to | ||
Example |
|
...
Name | FORCE_SC_ACCEPTED | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | When set to true, this property forces a 202 HTTP response to the client immediately after WSO2 EI the ESB profile receives the message so that the client stops waiting for a response. | ||
Example |
|
Anchor | ||||
---|---|---|---|---|
|
Name | DISABLE_CHUNKING | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | Disables the HTTP chunking for outgoing messaging If you set this to true, it disables HTTP chunking for outgoing messages. Instead, the ESB profile builds the message to calculate the content length and then sends the particular message to the backend with the content length (e.g., You can use this parameter if the client sends the request with HTTP chunking (i.e., with
| ||
Example |
|
...
Name | NO_ENTITY_BODY | ||
---|---|---|---|
Possible Values | none | ||
Default Behavior | In case of GET and DELETE requests this property is set to true. | ||
Scope | axis2 | ||
Description | This property should be set if a user wants to generate a response from WSO2 EI the ESB profile to a request without an entity body, for example, GET request.
| ||
Example |
|
...
Name | FAULTS_AS_HTTP_200 | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | When WSO2 EI receives a soap fault as a HTTP 500 message, WSO2 EI the ESB profile will forward this fault to client with status code 200. | ||
Example |
|
...
Name | REQUEST_HOST_HEADER | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | WSO2 EI The ESB profile will set hostname of target endpoint and port as the HTTP host header | ||
Scope | axis2 | ||
Description | The value of this property will be set as the HTTP host header of outgoing request | ||
Example |
|
...
Name | FORCE_POST_PUT_NOBODY | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | This property allows to send a request without a body for POST and PUT HTTP methods. Applicable only for HTTP Passthrough transport. | ||
Example |
|
Anchor | ||||
---|---|---|---|---|
|
Name | FORCE_HTTP_CONTENT_LENGTH | |||||
---|---|---|---|---|---|---|
Possible Values | "true", "false" | |||||
Default Behavior | false | |||||
Scope | axis2 | |||||
Description | This If the request sent by the client contains the ‘Content-Length’ header, this property allows the content length to be sent when WSO2 EI sends a request to a back end server. When HTTP 1.1 is used, this property disables chunking and sends the content length. When HTTP 1.0 is used, the property only sends the content length.This property should be set ESB profile to send the request with the content length (without HTTP chunking) to the back end server. You should set this to true in scenarios where the backend server is not able to accept chunked content. For example, in a scenario where a pass-through proxy is defined and the backend does not accept chunked content, this property should be used together with the COPY_CONTENT_LENGTH_FROM_INCOMING property, to simply add the content length without chunking. When HTTP 1.1 is used, this property disables chunking and sends the content length. When HTTP 1.0 is used, the property only sends the content length.
| |||||
Example |
|
...
Name | COPY_CONTENT_LENGTH_FROM_INCOMING | |||||
---|---|---|---|---|---|---|
Possible Values | "true", "false" | |||||
Default Behavior | false | |||||
Scope | axis2 | |||||
Description | This property allows the HTTP content length to be copied from an incoming message. It is only valid when the | |||||
Example |
|