Date: Fri, 14 Aug 2020 10:38:26 -0700 (PDT) Message-ID: <> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_149117_987920046.1597426706591" ------=_Part_149117_987920046.1597426706591 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html HTTPS Servlet Transport

HTTPS Servlet Transport

Similar to the HTTP transport, the HTTPS transport consists of a= receiver implementation which comes from the Carbon core component and a s= ender implementation which comes from the Apache Axis2 transport module. In= fact, this transport uses exactly the same transport sender implementation= as the HTTP transport. So the two classes that should be specified in the = configuration are org.wso2.carbon.core.transports.http.HttpsTransport= Listener and org.apache.axis2.transport.http.CommonsHTTPTransp= ortSender for the receiver and sender in the specified order. The co= nfiguration parameters associated with the receiver and the sender are the = same as in HTTP transport. This is also a blocking transport implementation= .

However, when using the following class as the receiver implementation, = we need to specify the servlet HTTPS transport configuration in the transpo= rt's XML file.

The class that should be specified as the transport implementation is org.wso2.carbon.server.transports.http.HttpsTransport. In additi= on to the configuration parameters supported by the HTTP servlet transport,= HTTPS servlet transport supports the following configuration parameters:


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

Parameter Name



Possible Values

Default Value


Transport level security protocol to be used.=





Path to the keystore which should be used for= encryption/decryption.


A valid file path to a keystore file



Password to access the specified keystore.


A valid password


Similar to the servlet HTTP transport, this transport is also based on A= pache Tomcat's connector implementation. Please refer Tomcat connector configuration reference for a complete list of supported para= meters.

Although the axis2.xml file co= ntains configurations for HTTP/S transports by default, they are not u= sed by WSO2 products. Instead, the products use the HTTP/S transport config= urations in Tomcat-level; therefore, changing the HTTP/S configurations in = the axis2.xml file has no effect.