Search results

Stupid question! It doesn't matter if content-encoding is br, gzip or deflate for cached files. Whenever 1 of these 3 kinds of content-encoding compressions is used lscache always compresses dynamic content, but not different depending on br, gzip or deflate. Only if there is no compression or...

If hosting would be okay there wouldn't missing almost everything what OLS/LSWS identifies. Take the board in front of your head away!

You are the one who understand complety nothing. You expect a proper working of your OLS, but the environment of your server misses almost everything of OLS and LSWS!

Do you have a board in front of your head or are you doing it on purpose? I'll show you what's wrong with your hosting and you insult me? What's wrong with you?

And what? You have OLS and you use LScache?! And anything else is missing!

Relax yourself :) Nobody wants to take anything away from you or attack you. If I'm speaking here, it's probably because there's no one else. This forum is lonely and poorly supported. Anyway, let's talk about logic. You complain that your "OLS" server doesn't work as you expect. Have you ever...

There is no "multiple times". If browser supports br, content-encoding is available with the first request. Where does this statement come from?

For static sources your server uses br for content-encoding, but this is only related to content-encoding and not for cached files. If I check your response headers your server displays "nginx" and not OLS as server software. Does your host use nginx as proxy in front of your hosting? Maybe this...

It seems you have any additional plugin installed that controlls the behaviour of the images and this conflicts with lazy load feature. If case this is a WooCommerce based page you get support for cache plugin only at Wordpress support page for cache plugin. This forum doesn't support LiteSpeed...

@mistwang Why don't you read previous same posts? This is nginx spam?

ngnix spam!

This feature already exists: https://docs.litespeedtech.com/lscache/lscwp/cache/#purge-all-on-upgrade

Don't think complicate, use it and enjoy to save data that has not to be unnecessary downloaded. All, but not LScache extension for OC use this method.

To purge the entire cache you can also use alternative ways and for this you don't have to use curl. Generate a blank PHP page and paste the code below to this file: header("X-LiteSpeed-Purge:*");

Again yes, but this is why request method has explicit to set to override HEAD requuest to GET method.

The next possible reason is that your licence has expired. If you have LiteSpeed web server running and there is no valid license every request will result in a 403 or LiteSpeed web server is switching to Apache.

.... and that's why request method GET has explicit to be set.

Again, request method has nothing to do with "CURLOPT_NOBODY". This curl option has affect on returning message body and depending on the value for this option the ouput of the request will be returned or not. For caching a page you don't need the return and that's why it is better to set value...

This is not a HEAD request. HEAD means only HTTP Header and no message body, but message body is not HTML body. That is a big difference. A only HEAD request prevents to cache a page.

You seem to talk about cache plugin settings of Wordpress? If so, you should know that these forum doesn't support cache plugins, even they are made by LiteSpeed itself. To get support for your issue please check this...