Search results

Have you tried the "Purge All" button in our wp cache plugin?

Make sure you cleared the cache before you do the no-cache test. Verify that "X-LiteSpeed-Cache: hit" is not set.

Have you verified the response header to make sure cache is really on? "X-LiteSpeed-Cache: hit" is set? either cache is not working properly, or something is slowing down the server. Do you have mod_security enabled?

Your test is likely network bounded, so it is really limited by network speed. But, you should be able to tell the difference by checking server load during the test.

something wrong, all response are non-2xx.

That's how cache works, to avoid hitting backend php script. If need to have stats updated when cache is used, the stats need to be updated through AJAX.

Later we will support variables in the configuration, can use So, you do not need to specify the real value, variable is based on virtual host configuration.

Yes, you should set it. it is a server level cache root configuration. if a vhost does not have its own cache root configured, the server level cache root will be used (shared among all vhosts). If all vhost has it own cache root configured, it does not matter much, but I still recommend to...

Yes, the purpose of per-user cache directory is for easy cache management, each user can easily purge all cache himself, just in case something went wrong. Now, if you use relative path for "CacheRoot" like The cache directory will be created as "lscache" under user's home directory. To use...

It looks like ApacheBench is used.

Right now we do not have a solution for this yet. It is bad PHP code, should use POST instead.

added.

Please update to the latest build of 5.0.13 /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.13

probably because directory auto indexing is enabled. If you switch back to Apache, will apache show this.

try adding to .htaccess, see if it can help or not.

I would just do it via browser developer's tool.

Maybe some static files was not served correctly when LiteSpeed is used. You can compare the content of related response between Apache and LiteSpeed.

ESI does not like compressed dynamic response, so you need to turn off compression from PHP for now. It will be addressed later.

It more likely means that some event triggered a cache flush.