Allowing HTTP and HTTPS call to public facing Hostname in Mashery

Allowing HTTP and HTTPS call to public facing Hostname in Mashery

book

Article ID: KB0082116

calendar_today

Updated On:

Products Versions
TIBCO Cloud API Management -

Description

Some customers may require both HTTP and HTTPS calls to be served by Mashery proxy. This requirement can be achieved by setting the endpoint with the configuration described in this article.

Issue/Introduction

This article can be followed to allow calls to Mashery proxy (Customer public hostnames) using HTTP and HTTPS methods.

Resolution

To allow calls with methods HTTP and HTTPS to be served by Mashery the configuration "Customize your Public Endpoint Address" should be set to HTTP with the proper hostname and URI. The following screenshot provides the configuration.

User-added image

The following calls can served using this configuration.

curl -v -i "https://api.mashery.com/datacenter/test/?api_key=<api_key>"

curl -v -i "http://api.mashery.com/datacenter/test/?api_key=<api_key>" 

To get the HTTPS call working the public hostname should have a valid SSL certificate. Article "000035175: Enabling SSL for client facing hostnames" provides details on the process of how to get SSL certificate uploaded for a client facing hostname hosted by Mashery.