Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

The transport receiver implementation of the HTTP transport is available in the Carbon core component. The transport sender implementation comes from the Apache Axis2 transport module. This transport is shipped with WSO2 Carbon and all WSO2 Carbon-based products, which use this transport as the default transport, except WSO2 ESB. The two classes which implement the listener and sender APIs are org.wso2.carbon.core.transports.http.HttpTransportListener and org.apache.axis2.transport.http.CommonsHTTPTransportSender respectively.

Tip
Info
titleNote
title
  • This is a blocking HTTP transport implementation, meaning that I/O threads get blocked while received messages are processed completely by the underlying Axis2 engine.
Info
  • Although the axis2.xml file contains configurations for HTTP/S transports by default, they are not used by WSO2 products. Instead, the products use the HTTP/S transport configurations in Tomcat-level; therefore, changing the HTTP/S configurations in the axis2.xml file has no effect.
Tip

In transport parameter tables, literals displayed in italic mode under the "Possible Values" column should be considered as fixed literal constant values. Those values can be directly put in transport configurations.

Transport Receiver Parameters

Parameter Name

Description

Requried Required

Possible Values

Default Value

port

The port number on which this transport receiver should listen for incoming messages.

Yes

A positive integer less than 65535

 

proxyPort

When used, this transport listener will accept messages arriving through a HTTP proxy server which listens on the specified proxy port. Apache mod_proxy should be enabled in the proxy server. All the WSDLs generated will contain the proxy port value as the listener port.

No

A positive integer less than 65535

 

When using org.wso2.carbon.core.transports.http.HttpTransportListener as the transport receiver implementation, HTTP servlet transport should be configured in the $PRODUCT_HOME/conf/transports.xml file. The transport class that should be specified in the transports.xml file is as follows:

Code Block

org.wso2.carbon.server.transports.http.HttpTransport

...

This is only a subset of all the supported parameters. The servlet HTTP transport uses the org.apache.catalina.connector.Connector implementation from Apache Tomcat. So the servlet HTTP transport actually accepts any parameter accepted by the connector implementation. Please refer to Apache Tomcat's connector configuration reference (http://tomcat.apache.org/tomcat-5.5-doc/config/http.html) for more information and a complete list of supported parameters.

Transport Sender Parameters

Parameter Name

Description

Requried

Possible Values

Default Value

PROTOCOL

The version of HTTP protocol to be used for outgoing messages.

No

HTTP/1.0, HTTP/1.1

HTTP/1.1

Transfer-Encoding

Effective only when the HTTP version is 1.1 (i.e. the value of the PROTOCOL parameter should be HTTP/1.1). Use this parameter to enable chunking support for the transport sender.

No

chunked

Not Chunked

SocketTimeout

The socket timeout value in milliseconds, for out bound connections.

No

A positive integer

60000 ms

ConnectionTimeout

The connection timeout value in milliseconds, for out bound connections.

No

A positive integer

60000 ms

OmitSOAP12Action

Set this parameter to "true" if you need to disable the soapaction for SOAP 1.2 messages.

No

true, false

false