LSCWP on LSCache server

[Hedloff]

If we set these settings on a ordinary Litespeed hosting server:

"
Set a storage path to LSCache.

Cache Policy Settings
Under “Cache Policy” set the following:

Enable Public Cache - No
Check Public Cache - Yes
Ignore Request Cache-Control - Yes

All other settings can be left as “Not Set”.
"

Will this effect other customers on the server that does not use the Wordpress cache plugin?
I mean, will something on the server be cached that should not be?

Before we had no storage path set and all settings under cache were set to "Not set".

 

[NiteWave]

Will this effect other customers on the server that does not use the Wordpress cache plugin?

should not affect other customers. since "Enable Public Cache - No"

you can test simplest phpinfo.php under other customers' document root. see if it's cached or not. should not be cached.
if cached, please report back to us.

 

[Hedloff]

Well, I tested alot of sites on the server and they are not caching.
But I just got a question from a customer about caching and when I checked his site it is affected by Litespeed cache.

And the customer is not even using Wordpress, but Drupal!
It started when I setup these settings customer said

 

[Hedloff]

Checking the response headers:

1. Server:
   LiteSpeed
2. Strict-Transport-Security:
   max-age=15768000
3. Strict-Transport-Security:
   max-age=15768000
4. Vary:
   Accept-Encoding
5. Vary:
   Cookie,Accept-Encoding
6. X-Drupal-Cache:
   HIT
7. X-LiteSpeed-Cache:
   hit
8. X-Powered-By:
   PHP/5.5.32
9. X-UA-Compatible:
   IE=edge,chrome=IE7

 

[Hedloff]

I checked another customer on the same server with Drupal 7.43 and that site is not using Litespeed cache or cached at all.
So maybee it has to do with this one customer is using Drupal cache?

 

[NiteWave]

what's your lsws version ?

 

[Hedloff]

Was 5.0.13, but upgraded to 5.0.14 but still the same

 

[mistwang]

when set
Check Public Cache - Yes

LiteSpeed cache may cache a page, if it claims to be public cacheable in the response header.

Or, that customer is playing with LiteSpeed cache control with rewrite rule.

 

[Hedloff]

So what your saying is that LSCache or LSCWP can't be used?
Customer with issues have to wait 1 day before they see what they posted on their website.

So we have to have a dedicated Wordpress server? That's bad....

 

[NiteWave]

Customer with issues have to wait 1 day before they see what they posted on their website.

explicitly disable lscache in document root .htaccess should fix the issue
<IfModule LiteSpeed>
CacheLookup public off
</IfModule>

 

[Hedloff]

Yes, that worked:

1. Server:
   LiteSpeed
2. Vary:
   Cookie,Accept-Encoding, Accept-Encoding
3. X-Drupal-Cache:
   HIT
4. X-Powered-By:
   PHP/5.5.32
5. X-UA-Compatible:
   IE=edge,chrome=IE7
   
   But we cannot check if each customer have enabled some kind of cache in their script/.htaccess file?
   Then LSCWP cannot be used on a shared hosting server and is useless.

 

[mistwang]

The best way to have it fix is let us to login to the server to check the drupal site to figure out why cache is triggered.
Please contact bug@litespeed

Our goal is to make lscache working well in shared hosting environment.

 

[NiteWave]

there may be a reasonable solution for your shared host.
for

Check Public Cache - Yes

you can set it to "No"

so by default, all sites are not cached. in your case, drupal will not be affected.

for those webistes user want to enable lscache, as the wiki tell, user should add
<IfModule LiteSpeed>
CacheLookup public on
</IfModule>
explicitly in .htaccess

at your(host) side, just configure the cache policy once.
at your customers side, they only need make one change in .htaccess
CacheLookup public on
and install lscache for wordpress plugin.
all other sites(drupal / joomla et) not affected.

 

[Hedloff]

The best way to have it fix is let us to login to the server to check the drupal site to figure out why cache is triggered.
Please contact bug@litespeed

Our goal is to make lscache working well in shared hosting environment.

You mean bug@litespeedtech.com ?

there may be a reasonable solution for your shared host.
for

you can set it to "No"

so by default, all sites are not cached. in your case, drupal will not be affected.

for those webistes user want to enable lscache, as the wiki tell, user should add
<IfModule LiteSpeed>
CacheLookup public on
</IfModule>
explicitly in .htaccess

at your(host) side, just configure the cache policy once.
at your customers side, they only need make one change in .htaccess
CacheLookup public on
and install lscache for wordpress plugin.
all other sites(drupal / joomla et) not affected.

Well, if that will work it would be great.
But why don't you add that in the plugin? So once the plugin is in installed that will be added automatically inside the .htaccess file?

 

[NiteWave]

automatically add/delete rules to .htaccess, I've seen this behavior in wp super cache/w3 total cache plugin.
if the plugin get more popular, I think more users will have this feature requests and I believe this feature will be added without doubt. the difficult part is: .htaccess may contains many other rules. it may be difficult to know where to add the rules into .htaccess. most likely you have to manually adjust the position of the added rules in .htaccess.

but at the moment, what I'd like to know, is above idea actually working well for your sever ? while it looks no problem, need feedback on production server. if it's ok, I'd suggest our team to update the wiki.

 

[Hedloff]

It worked fine to turn off Check Public Cache - to No and add this in .htaccess file for wordpress:

<IfModule LiteSpeed>
CacheLookup public on
</IfModule>

But that is not the most ideal solution.
Please check you bug email

Yes, supercache adds their lines in the .htaccess and it's in my experience quite random.
So I think you could add it in the top without any issues.