use cache

Hi,

in your page , you have cache-control: public, max-age=7776000 , please set it back to wordpress default value cache-control: no-cache,must-revalidate,max-age=0 first, this header will tell browser to cache the page

Best regards,

Looks like what you are talking about is not in the cache settings of litespeed. I have to do what you say.

correct, it’s not from LSCWP

by default WP page gives that to ensure the page won’t be cached by browser, but you have modified that way , please restore it to WP default status first.

can you tell me the basic steps to do this?

I hope I could tell you , but there are could be many different ways to modify this header , as I don’t know how did you do it , then I don’t know how to help you to undo it

you are talking about the problem I need to restore it to WP default status first.

Rather than resetting LiteSpeed’s cache settings?

yes , as I have explained in previous reply , that header will tell browser to cache the page , by that saying , it could be that server-side has already updated , but the client-side , as page is cached , then it doesn’t get update in time

you can try this otherwise around , use tools like gtmetrix , view your page first, and in its waterfall , you can check the http response header, make sure you see it shows x-litespeed-cache: hit , then post something , gtmetrix it again , and check the waterfall , it should then show x-litespeed-cache : miss

this will indicate the LiteSpeed cache has purged during the post

Actually, I don’t know much about the technical issues.
Right now, I’m just using the litespeed cache plugin and enabling the plugin and memcache features.
That’s all I’m using.
And the problem I’m having is that the content I update takes a long time for users to see.
So can you tell me the easiest way to fix it?
Like: Turning off features on Litespeed cache, or resetting the litespeed cache plugin can fix this

okay , first step

try it with cache plugin disabled , how it behaves ?

So there is no specific fix for this case?
And I have to disable all cache

well , I hope thing can be that easy , you say something , I reply something , problem solved

but it’s not , thing doesn’t work out that way , you , or let’s say , we as you and me , need to locate/narrow down where is the cause , and then seek how to deal with it

I’m sorry I don’t have magic finger to fix issue by touch it ??

First, I’m very sorry.
Really I understand that these questions take a lot of your time, so I want to ask quickly where is the fix, but after your reply, I am wondering is it because of litespeed cache or because wordpress.com
Finally, I just want to ask is this problem related to cache? let me learn and change.
Again, very sorry.

Hi,

is it because of litespeed cache or because wordpress.com

that’s precisely something I want to figure out first , that’s why I asked you , in previously reply to test with cache plugin disabled

that will narrow down the issue is from WP itself / something plugisn or from LiteSpeed Cache plugin

Best regards,

I’m so sorry, it was my fault, I think this problem is only cache related. And think your help is around litespeed only.

please follow my suggestion to try with cache plugin disabled , see how it behaves.