Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Table of Contents
maxLevel4
minLevel4
typeflat

Property: POST_TO_URI

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

Code Block
<property name="POST_TO_URI" scope="axis2" value="true"/>

Property: DISABLE_CHUNKING

Name

DISABLE_CHUNKING

Possible Values

"true", "false"

Default Behavior

false

Scope

axis2

Description

Disables the HTTP chunking for outgoing messaging.

Example

Code Block
<property name="DISABLE_CHUNKING" value="true" scope="axis2"/>

Property: CONTENT_TYPE

Name

CONTENT_TYPE

Possible Values

string

Default Behavior

none

Scope

axis2

Description

In situations, where the ESB is receiving HTTP response messages without the Content-type header, this property can be used to specify a default content type to be used. If no such content type is specified for responses, the ESB will default to application/octet-stream.

Example

Code Block
<property name="CONTENT_TYPE" value="text/xml" scope="axis2"/>

Property: NO_ENTITY_BODY

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

Code Block
<property name="NO_ENTITY_BODY" action="remove" scope="axis2"/>

Property: 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

Code Block
<property name="FORCE_HTTP_1.0" value="true" scope="axis2"/>

Property: HTTP_SC

Name

HTTP_SC

Possible Values

HTTP status code number

Default Behavior

none

Scope

axis2

Description

Set the HTTP status code.

Example

Code Block
<property name="HTTP_SC" value="true" scope="axis2"/>

Property: FAULTS_AS_HTTP_200

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

Code Block
<property name="FAULTS_AS_HTTP_200" value="true" scope="axis2"/>

Property: NO_KEEPALIVE

Name

NO_KEEPALIVE

Possible Values

"true", "false"

Default Behavior

false

Scope

axis2

Description

Disables HTTP keep alive for outgoing requests.

Example

Code Block
<property name="NO_KEEPALIVE" value="true" scope="axis2"/>

Property: REST_URL_POSTFIX
Anchor
REST_URL_POSTFIX
REST_URL_POSTFIX

Name

REST_URL_POSTFIX

Possible Values

A URL fragment starting with "/"

Default Behavior

In Case of GET requests, 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 RESTful manner. Useful when it is required to append a context to the target URL in case of RESTful invocations.

Example

Code Block
<property name="REST_URL_POSTFIX" value="/context" scope="axis2"/>

Property: REQUEST_HOST_HEADER

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

Code Block
<property name="REQUEST_HOST_HEADER" value="www.wso2.org" scope="axis2"/>