We have configed an API Gateway cluster with 2 nodes, one intranet hostname of one node is VPSZ-API-Gateway01 and another hostname is VPSZ-API-Gateway02, and we use load balancer Nginx for the API Gateway cluster, the external URL for the nginx will be https://api.jusdaglobal.com:443/gateway, on API Gateway Administration load balancer configuration, we have configed an HTTPS url : “https://api.jusdaglobal.com:443” to match the URL of nginx, but after creating a new API, the Gateway endpoint is still intranet host name “http://VPSZ-API-Gateway01:5555/…” instead of nginx url “https://api.jusdaglobal.com:443”, we hope that the url exposed by the API in the Gateway endpoint is consistent with the url of nginx, what should we do.
The screenshots of the API and Gateway Administration load balancer configuration are attached for your reference, thanks.
When we only enable HTTPS protocol in policy, the gateway endpoint URL of the API has only one HTTPS URL like “https://openapi.jusda.com:443/…”, which is exactly what we want, but when we call the API, an exception of “Transport protocol not supported…” will be reported. In this case, whether the HTTP protocol must be enabled in the policy? But the HTTP protocol is not enabled on nginx, we do not want to expose the service of HTTP protocol, how can we solve this problem.
