[ad_1]
We’re actively counting on Cloudflare caching for our web site pages to load quicker. Now we have a mechanism for caching person knowledge primarily based on person identifiers which stop Cloudflare to serve one person knowledge to a different.
For some purpose (we’re exploring), the Settings on Cloudflare cache guidelines have modified and all of our web site requests began to get the identical and just one person portfolio web page.
Once more, that was solely read-only to the portfolio, no one had the flexibility to do any edit actions as a result of they’d no permission to take action.
Proper after the incident was reported, we did put our web site in upkeep mode, purged and disable all of the Cloudflare caches. All person portfolio knowledge is protected and we’re going to provide you with the motion objects for stopping this sort of incident sooner or later.
[ad_2]
Source link