CDN and cache plug-in "fight" is the real culprit!

Have you ever wondered if the "This page contains too many redirects" error is caused by a misconfigured CDN or caching plugin? In this article, we'll get to the root of the problem and reveal CDN It also provides a set of directly executable troubleshooting and fixing solutions to help you quickly restore your site's normal access and SEO performance.

1. What does "This page contains too many redirects" mean?

"This page contains too many redirects" is a very common type of error in the operation of websites, which usually occurs when the browser loads a web page in a loop. When a user visits a page, the server keeps directing the request to another URL, and eventually the browser detects the loop and automatically stops loading and displays the message.

When the site is enabled CDN（This error is more likely to occur after a Content Delivery Network (CDN) or a caching plugin, as both intervene in the request and response paths of a page, and if not configured correctly, can result in a circular jump.

2. why CDNs or caching plugins cause redirect loops

In most cases, redirection loops are not caused by a single cause, but rather a logical conflict that arises when multiple layers of systems are stacked on top of each other. The following are the four most common scenarios.

2.1 Inconsistent HTTPS and HTTP settings

Many sites have HTTPS forced redirection enabled (e.g. 301 redirection in Nginx or .htaccess), but the CDN also has "forced HTTPS" enabled. If both ends perform redirects at the same time, they may trigger a loop with each other.

2.2 Domain name CNAME or source site configuration error

If the CDN node points to the wrong source site, or if the jump back to the CDN domain is still forced in the source site, the browser will repeatedly jump between the two addresses.

2.3 Cookie or cache rule errors

If the caching plugin incorrectly caches a response result with a redirect status code (e.g. 302) when saving the page cache, the next visit will return that jump response directly, creating an infinite loop.

2.4 Hybrid Cache Mechanism Conflicts

CDN, WordPress caching plugins (such as theWP RocketIf you don't distinguish the rules, the caches (LiteSpeed Cache, W3 Total Cache) and the server's own caches may overwrite each other or trigger the jump logic repeatedly.

3. How to troubleshoot the "this page contains too many redirects" problem

When troubleshooting, the problem should be gradually narrowed down by testing at four levels: browser, CDN, plug-in and server, in that order.

3.1 Using Browser Developer Tools

Open Chrome or Edge browser and press F12 → switch to Network options → Reload page. View the redirect chain (status code 301/302) to clearly see the path the request took to jump between different URLs, helping to quickly locate the loop point.

3.2 Temporary shutdown of CDN

Go to the CDN control panel (e.g. Cloudflare, Aliyun, Tencent Cloud CDN) and select Pause Proxy or Development Mode. At this time, the site traffic directly back to the source server, you can determine whether the problem is caused by the CDN configuration.

3.3 Disabling the Cache Plugin

existWordPressThe backend deactivates cache plugins such as WP Rocket, LiteSpeed Cache, and W3 Total Cache in turn, and then refreshes the page.
If the problem disappears, it means that the problem is in the plugin cache layer.

3.4 Clearing Browser and Server Cache

Browser-side: Clear cache and cookies.
Server-side: clean up plugin cache, object cache (e.g. Redis/Memcached) and CDN cache, and retest access paths.

4. Specific solutions for different causes

Next, we provide specific coping strategies for common scenarios.

4.1 HTTPS Jump Conflict Repair

Ensure that the forced HTTPS logic is implemented in one place only. If the CDN has HTTPS redirection enabled, disable the related rules on the server side. Set SSL/TLS mode to Full or Full (Strict) instead of Flexible in Cloudflare to prevent repeated jumps between HTTP/HTTPS.

4.2 Source and CNAME Configuration Checking

Verify that the source site address of the CDN is the real server IP or primary domain name, not the CDN cache layer domain name. Remove redundant CNAME records in the DNS control panel to prevent circular pointing.

4.3 Cache plugin settings adjustment

Disable the options of "Cache login page" and "Cache jump page" to avoid caching redirection status. Check whether the plug-in and CDN duplicate the functions of "page compression" and "automatic HTTPS jump". Clear the plug-in cache and regenerate the static page cache.

4.4 Cookie and Session Configuration Optimization

If the site has a member login or shopping cart system enabled, make sure that the relevant dynamic pages (e.g. /my-account/, /checkout/) are excluded from the caching rules.
Also, cookie compatibility should be set to prevent theCDNCache jumps with login status.

5. How to prevent the recurrence of the "too many redirects" problem

After fixing the problem, it is even more critical to take preventative measures.

Keep the jump logic uniform to avoid duplicate configurations.
All links and resources are unified using the HTTPS protocol.
Regularly use Screaming Frog orAhrefs Site AuditDetecting the 301 chain.
Access should be retested after each update of the CDN or caching plugin.
Use short-term caching or exclusion strategies for dynamic pages to avoid caching error bounces.

6. Concluding remarks

The real difficulty with the "this page contains too many redirects" problem is the complexity of the interaction between the multi-layer cache and the CDN. By systematically troubleshooting the configuration, cleaning up the cache and standardizing the redirect logic, most problems can be solved in a short time. For the use of WordPress,Cloudflareor similar CDN services, keeping the configuration simple and avoiding duplicate settings is key to ensuring stable website operation.

Contact Us
Can't read the tutorial? Contact us for a free answer! Free help for personal, small business sites!	Customer Service
① Tel: 020-2206-9892
② QQ咨询：1025174874
(iii) E-mail: info@361sale.com
④ Working hours: Monday to Friday, 9:30-18:30, holidays off