Caching AJAX requests

sadly no , ajax call was not meant to be cached by design , you can try use the Force Cache URI with the query string , but can’t if that will surely works

It worked forcing the URI, thank you!

Now could you just help with how to make it dynamic, I don’t understand if we can use wildcards or not, like:
/wp-admin/admin-ajax.php?action=my_action&unique_id=*&sessionType=*

• This reply was modified 10 months, 3 weeks ago by Mouk Lab.

no , it won’t support wildcard , you need to use partial matching , extract the unique string from it

Yeah I figured out… Thank you. It’s working now.

I just have a last question, private cache works well for me and loads of users, but for some users after they logged in they still see in the menu “Log in” instead of “Log out”, confirming they are indeed logged in.

I don’t want to use ESI because it’s a real pain to implement, and moreover it works well for me and some users.

Any idea?

please provide the report number

you can get it in toolbox -> report – > click “send to LiteSpeed”

Report number: MOAHHFEO

Report date:?01/10/2024 09:05:05

Some people switching from their unsupported browser (firefox, opera) got the issue fixed but some other got the issue on Chrome.

from report , you force it to public cache , that means it will be same among login users

No the homepage URL is not in the Force Public Cache settings. Users log in on the home page and then get the home page with the Login button again instead of log out button.

Sorry I forgot to mention that was about the homepage

hmmm? how do I register on your site ?

By clicking the register menu entry from the menu bar ??

oh right , I registered , but it seems display correct on me

any more specific steps I need to do to trigger it ?

meanwhile , can also try disable the object cache , see if it helps.

And if you click the menu entry My*** Profile, do you see your own profile or a random in cache?

it shows me like this

——

I see , you should NOT force public cache on these pages ,at least private cache

• This reply was modified 10 months, 2 weeks ago by qtwrk.

It’s not force cached. And the link is built on the homepage, it sends you directly to a user, it’s not like /my-profile, it’s /user-a
So should I exclude the entire homepage?

I actually don’t understand why do you even put them into force cache setting besides these admin-ajax