LiteSpeed Cache - Community

LiteSpeed Cache - Community 1.0.4.3

No permission to download
@John Blaze Apologies, forgot a part. Please add this line instead:
Code:
error_log('check server vars ' . print_r($serverVary, true));

@allewreK Could you please pm me temporary credentials to try to log in to your site? I'd like to see what is getting cached that causes this issue.

added new code and ran it again. I don't see anything under Server Logs on xenforo do I need to check somewhere else
 
Do you own your server or are you running your site through a hosting provider?

Possible error message locations:
/usr/local/apache/logs/error_log
/home/user/logs/error_log
/home/user/public_html/error_log (where the xenforo entry index.php is located)
 
Do you own your server or are you running your site through a hosting provider?

Possible error message locations:
/usr/local/apache/logs/error_log
/home/user/logs/error_log
/home/user/public_html/error_log (where the xenforo entry index.php is located)

i sent you a private message with download link to the error log. thanks in advance
 
To anyone that encounters John's issue:

The problem was the placement of the cache-vary rewrite rule. Please make sure to place it before the "last" flagged rewrite rules, otherwise those rules will not be hit.
 
Hello,

I am now using this addon in production, and it clearly improve load's time for visitors (so google too). That's amazing :)!


I have few questions :
  • If you cache a thread, let's say thread number 123.
    a) How long will it be cached ?
    b) If a new user like one of the post for this thread, will it be uncached ? Did you think about every actions (reply ? like ? unlike ? etc...)
    c) If a new user register on the board, will the thread stay in cache (since there is no link between the new user and this thread) ?
 
AllewreK,

a. That should be a configuration option.
b. I believe likes/dislikes/unlikes will not cause the cache to purge the page. We will take this into consideration. Replies will purge the cache.
c. Logged in users are not served from the cache because their pages typically contain private information.
 
AllewreK,

a. That should be a configuration option.
b. I believe likes/dislikes/unlikes will not cause the cache to purge the page. We will take this into consideration. Replies will purge the cache.
c. Logged in users are not served from the cache because their pages typically contain private information.

For the like/unlike cache purge, if you make a new option, I would suggest you to add an option to the ACP. Maybe some users don't want a like to purge the cache.
 
Hello there,

We have a WordPress front-end as well as XenForo - just wondering if this will work OK together with your WordPress plugin LiteSpeed Cache ?

Optic, as Recep mentioned, it should work. That said, if they are both in the same virtual host, you may experience some issues where non-logged-in pages are served to logged in users.

We suggest setting a login cookie in one of the CMS's. It'd be easier to set it in the WordPress plugin. In the wp admin, go to LiteSpeed Cache -> Settings -> Advanced -> login cookie. This can be set to like _lsc_wp or something, and there should be no more interference between the two.

Cheers,
Kevin
 
Thanks @lsKevin for your response. :)

Can I also ask if there is any ETA on the pro version?

From your FAQ, the free version doesn't cache logged in users:
Will there be a Pro version?
Yes, we plan on developing an enterprise version capable of supporting logged in users later this year.
 
Optic,

Unfortunately, we do not have a timeline for that. We are currently working on that on the WordPress side. That is near completion, but will likely result in a few bug reports, so I do not want to give you an estimate (like the one you linked) until we get closer to that point.
 
Can make it cache differently for different style? Currently it just override everything with the same cache.
 
@lsKevin I noticed that the LiteSpeed Cache Management tab is blank:
2016-12-20 17_48_54-Admin CP - Anime Forums.webp
(is this normal?)

But the settings using the sidebar link looks OK:
2016-12-20 17_49_41-Options_ Litespeed Cache _ Admin CP - Anime Forums.webp

Header looks OK for guests:
Code:
server:LiteSpeed
set-cookie:lsc_active=1
status:200
vary:Accept-Encoding
x-frame-options:SAMEORIGIN
x-litespeed-cache-control:public,max-age=300
x-litespeed-tag:H

This indicates a LSCache hit?
 
@bloh @Optic

Will reply to both of you at the same time because your questions are actually somewhat related :D

I'm not sure about the management tab. I'm 90% sure that it should've gone to the actions section. Could you check that to see if that is empty too?

In the actions tab, there should be a 'validate cache settings' button or similar. When I get the lab up and running, I'll edit this message to get the real name. This button will check any settings you have (e.g. if you have multiple languages or styles), and ask you to change your .htaccess file. This change is required so that the styles will cache and load separately.

Optic, I do not see a 'X-LiteSpeed-Cache: hit'. That's the header that indicates a cache hit. The headers you listed indicate that the plugin is working, but not the cache. Does your .htaccess file contain 'CacheLookup Public On'?

I hope I made this clear, will edit the post later to add more info.

Kevin
 
I'm not sure about the management tab. I'm 90% sure that it should've gone to the actions section. Could you check that to see if that is empty too?
I can't seem to find this Actions tab you're referring to sorry.

I reinstalled the add-on and now OK:
lsws-admin.webp

Yes I do have 'CacheLookup Public On' in .htaccess. In my LSWS config I have all the Cache settings set as "Not Set". Do I need to adjust any of these settings?
LiteSpeed WebAdmin Console.webp
 
Last edited:
Optic,

Glad reinstalling got that bit working :)

Thanks for reminding me! Yes, this may be because your storage path is not set. Depending on the type of install you have, the instructions are a little different, so here's a link that should contain a link to the correct setup guide.

For what it's worth, both the WordPress and XenForo portions of your site aren't getting cached, so it's likely not a XF or WP specific issue.

Kevin
 
I did add this as per instruction:

### LSCACHE START LOGIN COOKIE ###
RewriteRule .* - [E="cache-vary:xf_style_id"]
### LSCACHE END LOGIN COOKIE ###

But it didn't work.

Note that I'm using TMA mobile app to force load certain style for the app users. But then, the same cache is served across app & non-app users.
 
Back
Top Bottom