HTTP Transport Properties

Given below is a list of HTTP transport-specific properties.

Name	POST_TO_URI
Possible Values	"true", "false"
Default Behavior	false
Scope	axis2
Description	This property makes the outgoing URL of the ESB a complete URL. This is important when we talk through a Proxy Server.
Example	<property name="POST_TO_URI" scope="axis2" value="true"/>

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., `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"/>

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 removed if a user want to generate a response from the ESB to a request without an entity body, for example, GET request.
Example	<property name="NO_ENTITY_BODY" action="remove" scope="axis2"/>

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"/>

Name	HTTP_SC
Possible Values	HTTP status code number
Default Behavior	none
Scope	axis2
Description	Set the HTTP status code.
Example	<property name="HTTP_SC" value="200" scope="axis2"/>

Name	FAULTS_AS_HTTP_200
Possible Values	"true", "false"
Default Behavior	false
Scope	axis2
Description	When ESB receives a soap fault as a HTTP 500 message, ESB will forward this fault to client with status code 200.
Example	<property name="FAULTS_AS_HTTP_200" value="true" scope="axis2"/>

Name	NO_KEEPALIVE
Possible Values	"true", "false"
Default Behavior	false
Scope	axis2
Description	Disables HTTP keep alive for outgoing requests.
Example	<property name="NO_KEEPALIVE" value="true" scope="axis2"/>

Name	REST_URL_POSTFIX
Possible Values	A URL fragment starting with "/"
Default Behavior	In the case of GET requests with an address endpoint, this contains the query string.
Scope	axis2
Description	The value of this property will be appended to the target URL when sending messages out in a RESTful manner through an address endpoint. This is useful when you need to append a context to the target URL in case of RESTful invocations. If you are using an HTTP endpoint instead of an address endpoint, specify variables in the format of "uri.var.*" instead of using this property.
Example	<property name="REST_URL_POSTFIX" value="/context" scope="axis2"/>

Name	REQUEST_HOST_HEADER
Possible Values	string
Default Behavior	ESB 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	<property name="REQUEST_HOST_HEADER" value="www.wso2.org" scope="axis2"/>