3 ms·
This has broken publishing in our app, which purges the file from the Cloudflare cache when something is republished. We’re ignoring errors from the Cloudflare
by robinhouston 7y ago
This has broken publishing in our app, which purges the file from the Cloudflare cache when something is republished. We’re ignoring errors from the Cloudflare API, but that isn’t enough in this case because it isn’t returning an error – it’s just hanging till the request times out.
We’re pushing an emergency config change to skip the cache invalidation, which will stop it timing out but means republished projects won’t update (because the old version will still be cached).
Godspeed to the Cloudflare engineers who are presumably scrambling to fix this!
- darkerside 7y agoDo you not have some kind of task runner you can offload this to? That seems like it would be of general benefit.
- robinhouston 7y agoThe trouble with returning to the user before the cache has been purged is that they think it hasn’t worked, because they still see the old cached version.
- darkerside 7y agoI'm probably missing something but it sounds like cache invalidation happens on republishing, not on user request for content.
- robinhouston 7y agoYou’re absolutely right. But user requests for content are made directly to Cloudflare, not through the app, and it’s common for users to click directly through to the published content after republishing.
- darkerside 7y agoAh, that makes sense. You could store latest task status per content in your database and have a JavaScript component that polls and shows a message if cache invalidation is incomplete. But for how often Cloudflare goes down, it's probably not worth it.