Help Center/ Content Delivery Network/ FAQs/ Domain Name Settings/ After Force HTTPS Is Enabled, Why Are Parameters Missing in a POST Request When I Call an API Using HTTP?

Updated on 2024-08-15 GMT+08:00

View PDF

After Force HTTPS Is Enabled, Why Are Parameters Missing in a POST Request When I Call an API Using HTTP?

A 301/302 redirect is a practical way of redirecting requests from HTTP to HTTPS. If a client does not send a request to the new URL, parameters will be missing, causing no response. A browser can receive a response because the browser submits parameters again after receiving a 301/302 status code. Therefore, after the client receives a 301/302 status code, the client needs to send a request again with target parameters carried.

If you want to open up APIs and enable force HTTPS, you are advised to set the API to https://endpoint/{url} to prevent missing parameters during 301/302 redirect when an API request is sent.

Parent topic: Domain Name Settings

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot