@John Blaze Are you saying that your rewrite rules contain the rule, but the message is still displaying?
@allewreK The reason you cannot use that rewrite rule (and you should also turn Enable Public Cache back to not set) is because when it is 'on', the server will cache every request. This is incorrect behavior, as the XF plugin should tell the server what is cacheable and what is not (as an example, XF control panel - this was cached because of setting 'Enable Public Cache' to On).
When both are off, you mentioned that the cache was always missing. Is it possible that the site was very active at the time? If so, when someone posts a new reply, the front page will get purged. When I visited your site, I noticed that your TTL was set to 190 seconds. A short TTL is not needed as we should be clearing the cache every time someone makes an updated post anyway.
Let me know if this is still confusing,
Kevin
Do you still have "CacheLookup public on" in your rewrite rules?
CacheLookup Public On is required to look up from the cache.
The CacheEnable rule should not be there, as that one causes issues.
@John Blaze Are you saying that your rewrite rules contain the rule, but the message is still displaying?
John,
There are two possibilities that I am aware of that may cause this issue:
1. What version of the server are you using? An older version of the server may not include the quotation processing or passing it back to XF.
2. I see a RewriteBase in your rewrite rules. Does this mean that this .htaccess file is outside the xf installation? e.g. the htaccess is in /public_html/.htaccess, XF is installed in /public_html/kamal/.
Are either of these the issue?
library/Litespeedcache/ControllerAdmin/Manage.php
error_log('check server vars ' . $serverVary);
error_log('check server vars ' . print_r($serverVary, true));
We use essential cookies to make this site work, and optional cookies to enhance your experience.