Why Does a Website Return Different Errors From the Origin and the CDN?

A website may return a normal response from its origin server but an error through the content delivery network, or the reverse. Caching, firewall rules, TLS settings, origin health checks, and request transformations can make the two paths behave differently.

What to check

Capture the response status, timestamp, request path, and response headers for both routes. Compare CDN cache status, edge rules, origin logs, TLS mode, host header, and any bot or rate-limit policy. Avoid repeatedly bypassing controls on a production system.

Recommended next step

Identify the layer producing the error and adjust the specific configuration after reviewing security impact. Purge only affected cached content when needed, then verify both cached and uncached requests through the normal delivery path.

How Informatix Systems can help

Informatix Systems provides cloud hosting, CDN, and server management services. We can review the affected systems and workflow, help identify likely causes, and outline a practical implementation path. Contact us with the platform involved, when the issue began, and non-sensitive error details.