Problem description
Customers report a blank page when they access a webpage that is accelerated by Content Delivery Network (CDN). This prevents the page from loading correctly.
Troubleshooting
A white screen error is usually caused by an issue with loading static resources, such as JavaScript or CSS files. To start, compare the network requests from accessing the origin server directly with the requests from accessing the server through CDN.
Bind the domain name to the origin IP address in your local
hostsfile. Access the origin server directly and save the network requests as a HAR file.Access the same page through CDN and save the network requests as a HAR file.
Compare the two HAR files to identify the resource with the abnormal response.
If you confirm that the issue is caused by a resource cached by CDN, refresh the cache for the affected resource.
Check the CDN console for features that might affect resource requests, such as URL rewrite and following 302 redirects for origin fetch.
Solutions
If you have configured the feature to follow 302 redirects for origin fetch, disable the feature. For more information, see Follow 301/302 redirects for origin fetch.
Use the Refresh Cache API to refresh the cache for the affected page URL. Set the
Forceparameter totrue.NoteYou must use the Refresh Cache API to submit a refresh task. Using directory refresh or regex-based refresh in the console only marks the cached content as expired. This means that if the file on the origin server has not changed but its response headers have, a refresh from the console might still serve the old content. An API call with the
Forceparameter set totrueensures the content is purged from CDN nodes. For more information, see CDN cache refresh mechanism.