Page Rule effect is Bizarre

[AmarGS]

Rule 1→ .dogs.cat/
Browser integrity check: ON, Always Online: ON, Security Level: High, Cache level: Cache Everything, Edge Cache TTL: 7 Days

Rule 2→ .dogs.cat/wp-admin
Browser Integrity Check: ON, Security level: High, Cache Level: Bypass, Disable Apps, Disable Performance

Rule 3→ .dogs.cat/wp-login.php
Browser Integrity Check: ON, Security level: High, Cache Level: Bypass, Disable Apps, Disable Performance

This rule has been in effect from since I started using Cloudflare for my website

Never Faced any problem.

Recently there as an attack on my website…So now I have become very serious about security.

Today morning I learned that Page rule order has its effect

So, I changed the page rule order to this.

Rule 1→ dogs.cat/wp-login.php*
Browser Integrity Check: ON, Security level: High, Cache Level: Bypass, Disable Apps, Disable Performance

Rule 2→ dogs.cat/wp-admin*
Browser Integrity Check: ON, Security level: High, Cache Level: Bypass, Disable Apps, Disable Performance

Rule 1→ dogs.cat/*
Browser integrity check: ON, Always Online: ON, Security Level: High, Cache level: Cache Everything, Edge Cache TTL: 7 Days

I use strict full SSL

Caching parentage increased to 80% which used to be around 35%…

However, whatever changes I make that does not appear publicly until I purge caching

Also, in the browser where I am on my website dashboard, when I open a new tab try a load a page from my website, it does not show that I am already logged in

I changed *.dogs.cat → dogs.cat

After reading at Cloudflare Support article that

*.dogs.cat = dogs.cat

Please help…Where I am making a mistake

[imagevuex]

@AmarGS

Rule 1→ dogs.cat/*
Browser integrity check: ON, Always Online: ON, Security Level: High, Cache level: Cache Everything, Edge Cache TTL: 7 Days

Just so you aware, your combination of cache everything and edge cache TTL, means HTML pages output will get cached on the Cloudflare CDN.

@AmarGS

However, whatever changes I make that does not appear publicly until I purge caching

Therefore, since you are caching HTML pages, any changes you make will not display until you purge Cloudflare cache. You were not aware that your page rule in effect will cache pages?

@AmarGS

Also, in the browser where I am on my website dashboard, when I open a new tab try a load a page from my website, it does not show that I am already logged in

Yes, because you are caching WP pages on CDN, you will be served a cached version, which was likely requested by another visitor. Likewise, other visitors might get served a cached version where it says your name / logged in. You can’t use page-cache like this with wordpress unless you at least disable the login bar.

@AmarGS

I changed *.dogs.cat → dogs.cat

After reading at Cloudflare Support article that

*.dogs.cat = dogs.cat

Depends. dogs.cat will apply for http://dogs.cat and https://dogs.cat, but not for **www.**dogs.cat. That’s why you would need to use the *wildcard if you are using www- or another subdomain to server the website.

@AmarGS

Please help…Where I am making a mistake

You need to consider your third page rule and the implications of page-caching with “cache everything” and “edge cache TTL”. There is a reason caching of html is disabled by default. If you enable page caching on the CDN, your visitors (and you) will be served pages that were served from your server earlier on, perhaps to another visitor. Pages will not reflect your dynamic server requests.

[AmarGS]

A big thank you…Yes, I changed caching everything to standard…it worked…Again caching percentage jumped to 80% and updates are appearing instantly…awesome…

I have so far read more than a hundred of tutorial on how to set perfect page rule…Can’t believe …all of them were wrong about CACHING EVERYTHING

it must be STANDARD…

A big thank you again…

[AmarGS]