Search results

No, all rules are to get webp support. Remove 1 and cache will not work for webp.

No....

Should work with this version, so you could run this method on your server with cron, but you don't need Powershell.

Check curl version on your server: run curl --version

For this method you need Powershell (already installed on every Windows based computer) and you must run it from your local computer, because for this method you need curl (for windows) version newer than 7.33. curl is part of OS and most servers only have version 7.29 installed. With this...

This code doesn't work. Let's give it a try: Change the current one: RewriteCond %{HTTP_USER_AGENT} "iPhone|iPod|BlackBerry|Palm|Googlebot-Mobile|Mobile|mobile|mobi|Windows Mobile|Safari Mobile|Android|Opera Mini" [NC] RewriteRule .* - [E=Cache-Control:vary=ismobile] into: RewriteCond...

No, the UA of (mobile) Safari contains "Mobile" && Safari in e.a. iphone or ipad, but not "Safari Mobile", so it doesn't matter if you remove Safari Mobile. The problem is "Mobile" and can be found in every UA of a mobile device, also Android. This wouldn't be a fix.

The existing rewrite rule for mobile devices could cause a conflict with a new rule for Safari browser. Both rules contain "Safari", so you can't use the code for Safari browser to define a cache rule for this browser. At this moment I have no (quick) solution for you. It is possible, but this...

You can verify it by your own with: https://http2benchmark.org/ https://http2benchmark.org/guide.html

Tell me if you want an alternative method instead of LSCache crawler to warmup the cache. This way is up to 10 times faster than LScrawler, but you must be familiar with PhpMyAdmin, MS Powershell and cURL. LScrawler has some deficits, so it will take some time to get a better one.

Some guys can't be helped. You are one of those.....

A self-describing consequence.....

Yes, but purge cache before test. If you warmup the cache the way how to warmup must be modified to warmup the cache for Safari browser too.

I have good news and bad news. I found a way to make cache for logged in users available. This is the good news, but an application like a forum software have a lot of private content. Private content means a punch hole (ESI) for each content. Each punch hole reduces performance of cache. After...

Have you checked my code example?

30 - 40%!

For everybody who has same issue with Journal3 and Webp plugin if LScache is used, this issue can't be fixed by LScache plugin for OpenCart. Disable Lscache or Webp plugin, both are not compatible. To get Webp function work, this plugin must be re-developed to work with Client-Side-Includes...

I have no good news! I just wanted to finish developing when I found out some issues with cache warmup. That means cache for phpBB can't be warmuped by LScrawler or every other script driven function that simulates URL request like curl. - LScrawler doesn't support URLs with more than 1 query...

Cache lifetime for static sources is controlled by cache-control header in .htaccess or WP settings and cache for static sources will be cached by browser and not by LiteSpeed. That is not a LiteSpeed feature. See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control...

Price will be monthly. Cache for logged in users will not be possible. phpBB has very restrictive security policy that prevents using specific code within template, so cache will only be available for guests. I could overwrite it, but that would be against the philosophy of security of phpBB...