If I explain more of the basics of cacheing, I think you will perceive it as condescension. So I am trapped in a bit of a Catch-22. Talking with you has been largely non-constructive as you don’t have any feedback that makes my best solution better or any reason why it doesn’t work as the “best but not perfect” solution.
I would just suggest to anyone else who stumbles on this thread the way I did via searches and such to read what I said carefully and evaluate it since the official CF documentation on wordpress/woo would push you toward the pro tier by default when you can get great cacheing that is safe for dynamic content on the free tier.
Don’t mind the trolls!
Editing this post since the admins had to lock topic due to the toxicity of one user.
@Rubious I hope you read my posts and understand why the request is in itself not an expectation to have.
However, I will say this. You could test running multiple domains to the same wordpress with a plugin that allows for those domains to persist when entered from.
Then tell nginx to rewrite urls with cookies (like the worpress logged in cookie) to a seperate domain you have pointing to your site.
2 page rules:
- cache everything at primary.domain.mysite
- cache standard, use Origin headers, at redirect.domain.mysite (e.g. users.mydomain.com)