kinansy

@isaumya
brilliant help .

Can i add part of the word with *
because my login page is only 1 word, and the registration pages are generated from tutorlms

example:
/inter* … “if the login page is internal”
kids-regist*
parent-regist*

this is a login page and 2 other pages
https://drive.google.com/file/d/1OhlIZJKrCbm6kBWYViDiPe6wdO58wVqb

when I remove the / at the end and click save. it get back immediately

@isaumya

after I save, it is automatically changing to /loginx/

I decided to use the plugin settings to bypass my custom pages.

Does it matter /loginX or /loginX/ ?

Thanks @isaumya
i ll keep the security rules only.
the bypass cache >>> i ll leave the default plugin behavior to decide it.

I asked because in the settings i see Prevent the following URIs to be cached /wp-json* … so i thought what about the rest of wp-

By the way, your article explaining CF cache “expiry” and edge servers is the best i found while searching

do you mean the plugin by default caches the wp-content ?

currently i am already using the 3 free pages rules on cloudflare.
one of them is wp-* High security + Browser Integrity + bypass cache

now how can i cache wp-content ?

search pages are generated dynamically based on the user search response. So, if you cache that page and then publish a new article, it might not show up on the search page unless you purge the whole cache.

Wouldn’t this cause a purge for that page “Automatically purge the Cloudflare’s cache when something changes on the website” “Purge cache for related pages only – (recommended)”
Purpose is: I don’t mind caching courses page for guest users until a new course is added

@isaumya

for loggedin user the cache-control is set to no-cache, no-store, max-age=0 for the first text/html type request

So, the second page visit is served from cached?
if yes, will it get purged if the user answered a quiz or posted a comment

and the logged in users are also excluded from this rule “Cache-Control max-age it is 60” as well
is that correct ?

@isaumya Thanks for your time

Brilliant explanation

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 ?

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

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 ?

ok. so it starts only when we manually purge everything ?
if that is the case, i prefer to turn it off and when I manually purge i ll manually preload.