HTTP Transport Properties

[ 1 POST_TO_URI ] [ 2 FORCE_SC_ACCEPTED ] [ 3 DISABLE_CHUNKING ] [ 4 NO_ENTITY_BODY ] [ 5 FORCE_HTTP_1.0 ] [ 6 HTTP_SC ] [ 7 HTTP_SC_DESC ] [ 8 FAULTS_AS_HTTP_200 ] [ 9 NO_KEEPALIVE ] [ 10 REST_URL_POSTFIX ] [ 11 REQUEST_HOST_HEADER ] [ 12 FORCE_POST_PUT_NOBODY ] [ 13 FORCE_HTTP_CONTENT_LENGTH ] [ 14 COPY_CONTENT_LENGTH_FROM_INCOMING ]

HTTP transport properties allow you to configure how the HTTP transport processes messages, such as forcing a 202 HTTP response to the client so that it stops waiting for a response, setting the HTTP status code, and appending a context to the target URL in RESTful invocations.

POST_TO_URI

Name	POST_TO_URI
Possible Values	"true", "false"
Default Behavior	false
Scope	axis2
Description	This property makes the request URL that is sent from the ESB profile a complete URL. When set to `false` only the context path will be included in the request URL that is sent. It is important that this property is set to `true` when the ESB profile needs to communicate with the back-end service through a proxy server.
Example	`<property name="POST_TO_URI" scope="axis2" value="true"/>`

FORCE_SC_ACCEPTED

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 ESB profile receives the message so that the client stops waiting for a response.
Example	`<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>`

DISABLE_CHUNKING

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 profile builds the message to calculate the content length and then sends the particular message to the backend with the content length (e.g., `Content-Length: 25`). You can use this parameter if the client sends the request with HTTP chunking (i.e., with `Transfer Encoding:chunked`) although you need to send the message without HTTP chunking to the backend, or if you need to modify the message payload, which the client receives before sending it to the backend. This property might decrease performance since the messages get built per each invocation. Also, this property does not affect Callout mediators, whose chunking must be disabled separately.
Example	`<property name="DISABLE_CHUNKING" value="true" scope="axis2"/>`

NO_ENTITY_BODY

Name	NO_ENTITY_BODY
Possible Values	"true", "false"
Default Behavior	In case of GET requests this property is set to true.
Scope	Axis2
Description	Set this property if you want to do the following: check if an incoming request to the ESB mediation flow has an entity body or not check if an outgoing request/response generated from the ESB mediation flow has an entity body or not If using the PayloadFactory mediator, this property does not need to be manually set since it is done automatically by the mediator.
Example	`<property name="NO_ENTITY_BODY" value="true" scope="axis2" type="BOOLEAN"/>`

FORCE_HTTP_1.0

Name	FORCE_HTTP_1.0
Possible Values	"true", "false"
Default Behavior	false
Scope	axis2
Description	Force HTTP 1.0 for outgoing HTTP messages.
Example	`<property name="FORCE_HTTP_1.0" value="true" scope="axis2"/>`