Recently I implemented a bunch of Page Rules that increased the amount of our site that was cached by CloudFlare because I was noticing the majority of our traffic was still being served by our origin server instead of CloudFlare. Implementing a series of Page Rules that EXCLUDED all of our account/login sections and the backend admin sections of the site as well as INCLUDING a main https://midcenturywarehouse.com/* as a lowest priority Page Rule after all of the exclusions definitely helped solve this issue and now much more of the site was now being served by CloudFlare instead of the origin server so our page load times noticibly increased.
That’s great, except now I have a different problem.
On our site, users have to log in to their account (or create an account if they don’t already have one) before they can add anything to their shopping cart.
Creating the account is no problem. But after the user is logged in, they are still unable to add anything to their shopping cart IF the item they’re looking at has already been cached.
If the item they’re looking at has NOT been cached, then yes, they can add it to their cart without any problem. The problem only appears when looking at an item’s page that has been cached, or looking at anything item displayed on the home page (which of course has all been served from cache)
You can easily tell when a user will and won’t be able to add an item to their cart based on the login button text in the upper right corner of the screen - if it says “Create An Account” they will NOT be able to add the item to their cart (since the cached version is showing even though they are logged in) and if it says “Logged In As [Customer Name]” then they WILL be able to add the item to their account.
So my question is… what else do I need to implement in Page Rules to be able to allow the logged in user to add anything they want to their account whether that item’s page has been cached yet or not???