Behavior become weird
-
Hi,
I tried to purge all things.
But I don’t know what I done even tried to use the purge all.
Sometimes purge all working, sometimes not.
And even I would like to use toolbox to empty entire cache, but still something wrong(ex:some plugin had removed but still appear again or updated the plugin, WordPress still want me to update again)
It made me nut, please help!The page I need help with: [log in to see the link]
-
Hi, Rucifa,
I’m not exactly clear of what your concerns are, but purging does not remove plugins. It only removes cache. If there’s a plugin you no longer want to use, you’ll have to deactivate it. Please be more specific about your issues so that we can try to help you.
Regards.
Hi,
please check this page first, see if there is any hint
the doc didn’t mention about cloudflare, but since you have it on your domain , please also check the
cf-cache-statusheader and what is its value when you have that “reverting” issueBest regards,
Hi tenkstars
It might the “Purge function” didn’t worked. (I deactivated the plugin first then removed it.)
I’ll try qtwrk’s suggestion first.Hi,qtwrk
Here is the Response headers information:
age: 215
cache-control: max-age=31536000
cf-cache-status: HIT
cf-ray: 66ee8eb0dfdf0abe-KIX
content-type: text/html; charset=UTF-8
date: Wed, 14 Jul 2021 23:33:40 GMT
expect-ct: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
link: <https://cyrians.com/wp-json/>; rel=”https://api.w.org/”
link: </wp-content/litespeed/cssjs/1d524.css?46c8b>; rel=preload; as=style,</wp-content/litespeed/cssjs/2d8ad.css?1f4a8>; rel=preload; as=style,</wp-content/litespeed/cssjs/ce048.css?43fd9>; rel=preload; as=style,</wp-content/litespeed/cssjs/97578.css?5266a>; rel=preload; as=style,</wp-content/litespeed/cssjs/56ef4.css?701a0>; rel=preload; as=style,</wp-content/litespeed/cssjs/cb128.css?d1ebe>; rel=preload; as=style,</wp-includes/js/jquery/jquery.min.js>; rel=preload; as=script,</wp-content/litespeed/cssjs/3dee7.js?012a6>; rel=preload; as=script,</wp-content/litespeed/cssjs/8b45e.js?4f18d>; rel=preload; as=script,</wp-content/litespeed/cssjs/eb7e4.js?c300e>; rel=preload; as=script,</wp-content/litespeed/cssjs/a9aae.js?6eeb4>; rel=preload; as=script,</wp-content/litespeed/cssjs/e7930.js?c5821>; rel=preload; as=script
nel: {“report_to”:”cf-nel”,”max_age”:604800}
server: cloudflare
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
x-content-type-options: nosniffx-litespeed-cache: hit
Hope it can help you.
-
This reply was modified 4 years, 11 months ago by
JS.
Hi,
no , I mean the response header on wp-admin area , not in frontside
Best regards,
Hi, qtwrk
Sorry for wrong messages.
Here is wp-admin area’s response header information.
age: 1344
cache-control: max-age=31536000, must-revalidate
cf-cache-status: HIT
cf-ray: 66eed13f9a50aee5-KIX
content-security-policy: default-src https: injections.adguard.org ‘unsafe-eval’ ‘unsafe-inline’ data:
content-type: text/html; charset=UTF-8
date: Thu, 15 Jul 2021 00:19:06 GMT
expect-ct: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
expires: Wed, 11 Jan 1984 05:00:00 GMT
nel: {“report_to”:”cf-nel”,”max_age”:604800}
permissions-policy: geolocation=(self “”),
referrer-policy: strict-origin-when-cross-origin
referrer-policy: no-referrer-when-downgrade
server: cloudflare
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGINx-litespeed-cache-control: no-cache
x-xss-protection: 1;mode=block
Hope it can help, thank you.
cf-cache-status: HIT
this is the issue, you need to disable cloudflare cache on wp-admin area
as matter of fact, you should not enable cloudflare cache on your dynamic pages
Hi, qtwrk
It looks like normal now.(I need to verify the problem still on or not)
And the Response header information become:cache-control: no-cache, must-revalidate, max-age=0
cf-cache-status: DYNAMIC
cf-ray: 66eefcf7c8e00a96-KIX
content-security-policy: default-src https: injections.adguard.org ‘unsafe-eval’ ‘unsafe-inline’ data:
content-type: text/html; charset=UTF-8
date: Thu, 15 Jul 2021 00:48:58 GMT
expect-ct: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
expires: Wed, 11 Jan 1984 05:00:00 GMT
nel: {“report_to”:”cf-nel”,”max_age”:604800}
permissions-policy: geolocation=(self “”),
referrer-policy: strict-origin-when-cross-origin
referrer-policy: no-referrer-when-downgrade
server: cloudflare
set-cookie: RtYidjcyJhuWeSLZ=OpIKibQn16kqNt%5DA; expires=Fri, 16-Jul-2021 00:48:57 GMT; Max-Age=86400; path=/; secure
set-cookie: kFGQoKLTVMJ=O28xf9%5BloR; expires=Fri, 16-Jul-2021 00:48:57 GMT; Max-Age=86400; path=/; secure
set-cookie: LCbEK-ePGNOqmd=cdXT_jQ; expires=Fri, 16-Jul-2021 00:48:57 GMT; Max-Age=86400; path=/; secure
set-cookie: cerber_groove=e3fc0c33a62f0d5be392d9d64b6836af; expires=Fri, 30-Jul-2021 00:48:58 GMT; Max-Age=1296001; path=/; secure
set-cookie: cerber_groove_x_ikAySTnse1vXgIl9x0LzEJVFu=CuPtpX1HBaFqo89Q3zY5Zm6Jge; expires=Fri, 30-Jul-2021 00:48:58 GMT; Max-Age=1296001; path=/; secure
set-cookie: cerber_groove=e3fc0c33a62f0d5be392d9d64b6836af; expires=Fri, 30-Jul-2021 00:48:59 GMT; Max-Age=1296001; path=/; secure
set-cookie: cerber_groove_x_ikAySTnse1vXgIl9x0LzEJVFu=CuPtpX1HBaFqo89Q3zY5Zm6Jge; expires=Fri, 30-Jul-2021 00:48:59 GMT; Max-Age=1296001; path=/; secure
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGINx-litespeed-cache-control: no-cache
x-xss-protection: 1;mode=block
Hope it can help you, thank you.
x-litespeed-cache-control: no-cache
cf-cache-status: DYNAMIC
cache-control: no-cache, must-revalidate, max-age=0it’s not even LiteSpeed cache plugin related issue , but yes, these are expected headers
Hi, qtwrk
I tried several hours and it worked.
Thanks anyway! -
This reply was modified 4 years, 11 months ago by
The topic ‘Behavior become weird’ is closed to new replies.