By default, it is set to off because a lot of time people don’t need it (who have a wp site but not a blog). You can turn it on if you want to avail the feature. Each settings item has a small blurb of tech below it explaining what it does.
I imagine in LMS, when teacher publish an announcement , it is similar to blog post. isnt it ?
another example is, buddyboss groups and forums
In LMS, Groups and Forums, most people who interact on the pages are loggedin users and for loggedin users the initial HTML request won’t be cached on Cloudflare and instead will be bypassed to be processed on the origin server. As a loggedin user can make many dynamic requests and pages can be shown dynamically to them based on many variables.
Thats why for loggedin users the plugin won’t cache the initial HTML request. Cached pages are only be served for non-loggedin users.
I imagine in LMS, when teacher publish an announcement , it is similar to blog post. isnt it ?
– Yes, technically it should be.
the plugin won’t cache the initial HTML request
only the initial html request?
I need to exclude all requests of logged in users not just the initial one.
can I control this ?
I think i know what you mean by the
for loggedin users the plugin won’t cache the initial HTML request
you mean the static files of the page. while the dynamic will always be excluded
thanks
last question on this topic please.
if there is a file that shows only for logged in users but it is same for all of them.
For example, site.com/wp-content/plugins/Xplugin/assets/images/register-pic.png
after this gets hit by first user. Will the next user hit it from CF ?
and how can we extend its cached age, as it might never be changed ?
only the initial html request?
I need to exclude all requests of logged in users not just the initial one.
can I control this ?
– When a user is loggedin the plugin will set no-cache cache-control header for the initial request that is of type text/html so it will be bypassed and served from your origin server but the static files will still be cached by Cloudflare.
after this gets hit by first user. Will the next user hit it from CF ?
– As I said the static file will always be cached by Cloudflare even for loggedin users.
and how can we extend its cached age, as it might never be changed ?
– Inside the plugin settings under the cache tab there is a section to add browser cache rule for static files. You can enable that as it will add the best cache control headers for the static files.
@isaumya Thanks for your time
Brilliant explanation
