Require HTTP / HTTPS
If you have a native API that requires clients to communicate with the server using the HTTP and/or HTTPS protocols, you can use the Require HTTP / HTTPS protocol action.
This action allows you to bridge the transport protocols between the client and the Mediator. For example, suppose you have a native API that is exposed over HTTPS and an API that receives requests over HTTP. In this situation, you can configure the API’s Require HTTP / HTTPS action to accept HTTP requests and configure its Routing action to route the request to the native API using HTTPS.
Input Parameters
Protocol | String. Specifies the protocol over which the Mediator accepts requests from the client. Note: | CentraSite supports HTTP version 1.1 only. |
Important: | Before you deploy an API over HTTPS, ensure that the Integration Server on which the Mediator is running has been configured for SSL. In addition, make sure you specify an HTTPS port in the Mediator’s Ports Configuration page. (In the Integration Server Administrator, go to Solutions > Mediator > Administration > General and specify the port in the HTTPS Ports Configuration field.) For details on the Port Configuration page, see Administering webMethods Mediator .) |
|
| Value | Description |
| HTTP | Default. Mediator will only accept requests that are sent using the HTTP protocol. |
| HTTPS | Mediator will only accept requests that are sent using the HTTPS protocol. |
| You can select both HTTP and HTTPS if needed. |
SOAP Version | String. For SOAP-based APIs. Specifies the SOAP version of the requests which the Mediator accepts from the client. |
Value | Description |
| SOAP 1.1 | Default. Mediator will only accept requests that are in the SOAP 1.1 format. |
| SOAP 1.2 | Mediator will only accept requests that are in the SOAP 1.2 format. |
HTTP Methods | String. For REST-based APIs. Specifies the HTTP methods in incoming requests which the Mediator accepts from the client. |
Value | Description |
| GET | Mediator will only accept GET invocations for the native API. |
| PUT | Mediator will only accept PUT invocations for the native API. |
| POST | Mediator will only accept POST invocations for the native API. |
| DELETE | Mediator will only accept DELETE invocations for the native API. |
| You can select more than one HTTP method if needed. Note: | It is important to specify all the HTTP methods that are supported for the API. For example, if the API is deployed to Mediator and you selected only the GET method in its Straight Through Routing action, then Mediator will only permit GET invocations. In this case, POST requests will be rejected with a return of Status Code 405 even if the native API happens to support POSTs. |
|
