how do you exclude logged in users. cant see it in settings

while reading FAQ, i see that plugin will add swcfpc=1 to each link of logged in users.

in Prevent the following URIs to be cached, i can see
*ao_speedup_cachebuster*

is this how you exclude the logged in users ?

where in the settings i can find excluding the logged in users ?

– Logged-in users are excluded from cache by default you don’t have to do anything. It’s totally out of the box.

do i need to exclude my custom login page ?

– Yes if you use a custom path for the login page.

`while reading FAQ, i see that plugin will add swcfpc=1 to each link of logged in users.

in Prevent the following URIs to be cached, i can see
*ao_speedup_cachebuster*

is this how you exclude the logged in users ?`

– That’s a cache buster which is used if you are using the default page rule mode. If you enable the worker mode inside the plugin settings, it won’t use the cache buster.

thanks for your quick answer. i know it is by default just wanted to understand how.

so is it slightly better for performance to use worker mode instead of inserting that buster in every generated URL ?

so is it slightly better for performance to use worker mode instead of inserting that buster in every generated URL ?

– Cache buster will only be added for loggedin users if you use the page rule mode. If you want to get rid of that then you have to use the worker mode.

But CF workers are not 100% free. It has a free tier.

but am i correct that it would be slightly better for performance instead of adding that to each URL

i can see workers limits here
https://developers.cloudflare.com/workers/platform/limits
what will happen if we reach that limit ? get Cloudflare 1015 error page ?
it is ok to receive that error but the most important is not stop the worker and start caching the logged in users

but am i correct that it would be slightly better for performance instead of adding that to each URL

– Performance wise no. The result will be same. Worker just going to give you more option and feature but in most cases, you don’t need it if you can live with that cache buster.

what will happen if we reach that limit ? get Cloudflare 1015 error page ?

– yes

it is ok to receive that error but the most important is not stop the worker and start caching the logged in users

– if you get that error the worker will stop working and none of your pages will get cached be it for admin or normal users. But CF gives a quile high limit even on the free plan. Basically 100,000 requests/day or 1000 requests/min

very helpful information

what happens if a user deletes that added buster in the URL, will they get in a cached version ?

what happens if a user deletes that added buster in the URL, will they get in a cached version ?

– Yes. If a logged-in user manually deletes that cache buster from the URL they will see the cached version of the page.

and the cached version can be of another user ?

?? thank you for the long discussion but it is really very useful

and the cached version can be of another user ?

– The cached version is what all non logged in users will see