asked on Caching errors with Edgecast CDN
Hi,
An online retail company is using Edgecast's CDN and somehow certain CSS files are continually being 'half loaded' into cache, ie. It loads half the file into cache and then stops (as if it is interrupted) at a point. So the cache then serves this incomplete file as the new legitimate cache and users see a 'misshaped' front end. This problem remains until the support team manually clear the cache and it loads the full CSS file correctly.
The CDN support team point to the app devs, and vice versa.
Could anyone suggest any troubleshooting, or how to track down whether it is the App or the CDN causing such an error?
Thank you
An online retail company is using Edgecast's CDN and somehow certain CSS files are continually being 'half loaded' into cache, ie. It loads half the file into cache and then stops (as if it is interrupted) at a point. So the cache then serves this incomplete file as the new legitimate cache and users see a 'misshaped' front end. This problem remains until the support team manually clear the cache and it loads the full CSS file correctly.
The CDN support team point to the app devs, and vice versa.
Could anyone suggest any troubleshooting, or how to track down whether it is the App or the CDN causing such an error?
Thank you
Web DevelopmentWeb ServersContent Management
Last Comment
Shalom Carmel
Are they using their own origin, or the Edgecast storage?
ASKER
I believe they are using their own origin, hosted on dedicated chunky hardware.
In my (extensive) experience the problem is usually on the origin side.
Are the loading the assets to cache as a workaround? On the purge/load tab, there is an option to pre-warm the cache with a valid object, there is also a simple API,
If they have the rules engine, try to debug the cache state using the "Debug Cache Response Headers" feature.
Are the loading the assets to cache as a workaround? On the purge/load tab, there is an option to pre-warm the cache with a valid object, there is also a simple API,
If they have the rules engine, try to debug the cache state using the "Debug Cache Response Headers" feature.
ASKER
thanks for the suggestions. I will have a look at those.
in your experience, are there any 'typical problems' on the client side that could be causing this? Locked files, script jobs, loading timeouts, etc.?
thanks again
in your experience, are there any 'typical problems' on the client side that could be causing this? Locked files, script jobs, loading timeouts, etc.?
thanks again
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.