However, there are cases where this won't work. For example, if you have an e-commerce site with dynamic elements like a shopping cart, header, checkout, and account pages, Cloudflare will show the user whatever they have cached, removing the dynamic elements for those pagessections. In the worst case, users will start seeing other users' shopping carts and account pages!
There are ways around this. One is to use AJAX to load these dynamic elements on the client side. WooCommerce is a great example of this, as most of the shopping cart elements are actually AJAX-based. If you use this, Cloudflare will serve the HTML to the user, but then the browser will work asynchronously with the origin server to populate the dynamic parts of the site.
However, if this is not the case, you will have to create a user india mobile database cache or bypass the edge cache based on a cookie that specifies whether the user is logged in or not.
Thankfully, most CMS have a cookie you can use to bypass the cache; you can see an example for WordPress here . The bad news is that this is a Business plan feature, so it costs £200 per month to have it (along with other great features).
Solving this problem with Cloudflare Workers
However, you can work around this by using Cloudflare workers .
An example worker that does this can be found here . It also comes with a handy WordPress plugin to add support for the headers that the worker uses to determine if the cache should be bypassed.