Enable HTTP/HTTPS

Edit online

This policy specifies the protocol to use for an incoming request to the API on webMethods API Gateway. If you have a native API that requires clients to communicate with the server using the HTTP and HTTPS protocols, you can use the Enable HTTP or HTTPS policy. This policy allows you to bridge the transport protocols between the client and webMethods API Gateway.

For example, you have a native API that is exposed over HTTPS and an API that receives requests over HTTP. If you want to expose the API to the consumers of webMethods API Gateway through HTTP, then you configure the incoming protocol as HTTP.

The table lists the properties that you can specify for this policy:
Property Description
Protocol Specifies the protocol (HTTP or HTTPS), SOAP format (for a SOAP-based API) to be used to accept and process the requests.

Select one of the following:

  • HTTP. webMethods API Gateway accepts requests that are sent using the HTTP protocol. This is selected by default.
  • HTTPS. webMethods API Gateway accepts requests that are sent using the HTTPS protocol.
SOAP Version For SOAP-based APIs.

Specifies the SOAP version of the requests which the webMethods API Gateway accepts from the client.

Select one of the following:
  • SOAP 1.1. This is selected by default. webMethods API Gateway accepts requests that are in the SOAP 1.1 format.
  • SOAP 1.2. webMethods API Gateway accepts requests that are in the SOAP 1.2 format.
SOAP version validation enabled For SOAP-based APIs.

Specifies whether webMethods API Gateway should only accept the request that includes the specified SOAP version.

If this option is selected, it is set as true and webMethods API Gateway accepts only the requests that include the specified SOAP version. The non-selected protocol is rejected with an error.

If this option is not selected, it is set as false and webMethods API Gateway accepts both the SOAP versions.