Similar to the HTTP transport, the HTTPS transport consists of a receiver implementation which comes from the Carbon core component and a sender 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.HttpsTransportListener and org.apache.axis2.transport.http.CommonsHTTPTransportSender for the receiver and sender in the specified order. The configuration 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 transport's XML file.
org.wso2.carbon.core.transports.http.HttpsTransportListener
The class that should be specified as the transport implementation is org.wso2.carbon.server.transports.http.HttpsTransport. In addition to the configuration parameters supported by the HTTP servlet transport, HTTPS servlet transport supports the following configuration parameters:
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.
Parameter Name | Description | Requried | Possible Values | Default Value |
|---|---|---|---|---|
sslProtocol | Transport level security protocol to be used. | No | TLS, SSL | TLS |
keystore | Path to the keystore which should be used for encryption/decryption. | Yes | A valid file path to a keystore file |
|
keypass | Password to access the specified keystore. | Yes | A valid password |
|
Similar to the servlet HTTP transport, this transport is also based on Apache Tomcat's connector implementation. Please refer Tomcat connector configuration reference for a complete list of supported parameters.