...
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 the current execution thread finishes, so that the client stops waiting for a response. | ||
Example |
|
| Anchor | ||||
|---|---|---|---|---|
|
Name | DISABLE_CHUNKING | ||
|---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | If you set this to true, it disables HTTP chunking for outgoing messages. Instead, the ESB 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 | 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 the ESB 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 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 |
|
...