Help Center/
API Gateway/
Best Practices/
API Openness/
HTTP-to-HTTPS Auto Redirection with a Dedicated Gateway/
Implementation Procedure
Updated on 2024-11-27 GMT+08:00
Implementation Procedure
Prerequisites
- You have created an API whose frontend request protocol is set to HTTPS or HTTP&HTTPS.
- The API has been published.
- An independent domain name and SSL certificate have been bound to the API group to which the API belongs.
For details about these operations, see the APIG User Guide
Enabling Redirection
- Log in to the APIG console, and choose API Management > API Groups.
- Click a group name to go to the details page.
- On the Group Information tab, locate the bound independent domain name, and enable HTTP-to-HTTPS Auto Redirection.
Verifying Redirection
- Use a browser to call the API through HTTPS.
- In the address bar of the browser, enter https://API request path, and press Enter.
- Press F12.
- Check the status code displayed on the Network tab. 200 means the calling is successful.
- Use a browser to call the API through HTTP.
- In the address bar of the browser, enter http://API request path, and press Enter.
- Press F12.
- Check the status code displayed on the Network tab. 301 means the redirection is successful.
Parent topic: HTTP-to-HTTPS Auto Redirection with a Dedicated Gateway
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot