Help Center>
Content Delivery Network>
FAQs>
Troubleshooting>
Why Does the System Always Display "301" After HTTPS Is Configured for a Domain Name?
Updated on 2024-04-17 GMT+08:00
Why Does the System Always Display "301" After HTTPS Is Configured for a Domain Name?
Origin Protocol is set to HTTP for the domain name on the CDN console but Force HTTPS is enabled on your origin server.
You need to set Origin Protocol to Same as user under the Origin Settings tab of your domain name on the CDN console.
Parent topic: Troubleshooting
Troubleshooting FAQs
- Why Am I Seeing a Message Indicating that the Domain Name Already Exists When I Add a Domain Name for CDN Acceleration?
- Why Is My Domain Name Inaccessible After HTTPS Secure Acceleration Is Configured?
- Why Is Data Obtained from a CDN PoP Not the Updated Data?
- Why Is 304 Returned When a User Accesses a Resource Under My Acceleration Domain Name?
- Why Is the Accelerated Page Incorrect Even Though I Can Access the Origin Server?
- Why Can't a Web Page Be Properly Displayed After the Origin Server's IP Address Is Changed?
- Why Do I Get an Access Failure and Access-Control-Allow-Origin Error?
- Why Does the System Always Display "301" After HTTPS Is Configured for a Domain Name?
- Why Do I Get Request Timed Out When Trying to Ping an Acceleration Domain Name?
- Why Are Incorrect Resources Being Pulled from My Origin Server?
- Why Is My Site Slow the First Time I Access It After CDN Is Configured?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more
