Litespeed causing issue with menu

But it doesn’t influence the server side cache. All in all this code forces to download the data from the server although the data are in browser cache, but this is not a cache plugin issue. This is the “nature” of HTTP.

My first code already tried to narrow it down and should make the change for cache-control only for logged-in users, but the issue already starts before login.

The reason for this issue is based on a LiteSpeed web server feature. The LSWS takes advantage of a technique available in the HTTP protocol. This technique is used to influence the loading behavior of the main document by telling the browser whether it should load the requested source or whether the browser should use the data from its browser cache because nothing has changed since the last request. Sounds positive at first, because it has a beneficial effect on the loading time. In this specific case, however, this has disadvantages. If a user is not logged in, the browser remembers that it does not have to load the accessed data again. After logging in, the user is redirected to the start page. However, he has the data for the start page in the cache because the web server has told him in advance that the data does not have to be reloaded again. This explains why a registered user sees “Login” in the account menu, precisely because this is the content from the browser cache.

The problem now is that the changed cache behavior is very difficult or impossible to narrow down. To do this, the web server would have to know before the login page is called that the user wants to log in. If the web server knew this, it could tell the browser in advance that it would have to reload the page accessed when it visited it again.

At the moment I can only think of 2 solutions:
1.) You only change the cache control parameters for the start page. All other pages remained unaffected by this change.
2.) You append a $_GET parameter to the forwarding URL after login, e.g. ?12345678. This parameter forces the browser cache to reload the page data from the server.

the 2 suggestions won’t work because the issue is not only related to the start page. It’s all pages visited before the user logs in.

Why not? Let’s narrow it down to start page. This would have no big impact and would only affect the homepage.

There must be thousands of membership WordPress websites running on Litespeed servers.

I don’t think so. This issue only happens

1.) on startpage and if startpage has already been requested before login

2.) with 3rd plugin for login/register.

Apologies for the late reply, I did not get a notification for your last message.

I’m sorry, but I was so engrossed in my work to build the best and fastest cache crawler that I completely forgot about you! Ashes on my head! 😉

The problem is not only related to the home page, it’s related to all the pages visited before logging in.

Right, but you said that you are always redirected to the start page after logging in. So it is enough to focus on the start page.

I disabled all my plugins yesterday and switched to one of the default themes (twenty twenty), then tried logging it with the “default” login and the issue was still present.

Hm… The plugin support has to deal with this.

In my mind there is nothing fix, but cache plugin should get an extra function. This function is for WP only that have a login and does the same what I gave you with the code in .htaccess. There is no other way to “fix” it.

Are you ready for a last “trick”? 😉

Shure? or Shure!