How Do I Solve the Problem of Excessive Redirection Times?
After a domain name is connected to WAF, if the system displays a message indicating that there are excessive redirection times when a user requests to access the target domain name, the possible cause is that you have configured forcible redirection from HTTP to HTTPS on the backend server and forwarding from HTTPS (client protocol) to HTTP (server protocol) is configured on WAF, WAF is forced to redirect user requests, causing an infinite loop. You can configure two pieces of server information about HTTP (client protocol) to HTTP (server protocol) and HTTPS (client protocol) to HTTPS (server protocol). For details, see Editing Server Information. Figure 1 shows the finished server settings.
Troubleshooting Traffic Forwarding Exceptions FAQs
- How Do I Troubleshoot 404/502/504 Errors?
- Why Am I Seeing Error Code 418?
- Why Am I Seeing Error Code 523?
- How Do I Solve the Problem of Excessive Redirection Times?
- Why Am I Seeing Error Code 414 Request-URI Too Large?
- What Do I Do If the CPU Usage of the Origin Server Reaches 100%?
- What Is the Connection Timeout Duration of WAF? Can I Manually Set the Timeout Duration?
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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore