Search results

no, why? LiteSpeed Webserver is not the problem. The cache seems to be the problem.

If you are on shared hosting ask your provider if your host uses a CDN like Cloudflare or a proxy. If nothing helps try to overwrite this header in .htaccess header add X-Turbo-Charged-By "Name of your choice"

To me the same, because no LiteSpeed plugin caches. Each plugin is only a control panel to control and manage the cache. Caching itself will only be done by Lscache, a LSWS based cache engine.

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Can't confirm, everything looks okay.

This is a PHP related question not operating system and will be handled by your server control software like cPanel, Plesk and other.

Again, LiteSpeed Enterprise doesn't add "X-Turbo-Charged-By" header and there is no setting in WebAdmin console to disable or enable it. In WebAdmin you can only control if Server header should appear or not. This setting is what @Pong already noticed. If you have header "X-Turbo-Charged-By"...

X-Turbo-Charged is not a default header in LiteSpeed Enterprise. Check your headers again and look for "Server" header. If you really have LiteSpeed Enterprise Server header must be "LiteSpeed", but most of the time it is Cloudflare or a nginx proxy is used.

Have you OpenLiteSpeed?

PrestaShop has setting for mobile view, but is disabled by default, so check settings in configuration tab in LiteSpeed plugin, but purge LiteSpeed cache after you have enabled it. Purge cache button is on top of page header in the upper right corner.

@ryanhallinger "X-Turbo-Charged-By" what? Would you provide us with the name?

Header unset [Header Name]

If you want to get help, you must provide with this information. This single PHP file doesn't help to get answers.

To prevent missunderstanding: 1.) Is this image processing a pure PHP function or a combination PHP/Javascript? 2.) Does it work if Javascript is off?

Yes..... I believe ;)

Of course, there is support in lscache for webp images, but you don't want to have this solution. You asked for Retina detection.

Okay, I give up. You are right and I am wrong.... But for everybody else who is thinking like this collegue, this is neither a LSWS nor a Lscache issue....

Either we are in a loop or you don't want to understand why you can't detect Retina display. Also Journal can't. To me, Journal doesn't detect Retina display, it detects screen resolution by CSS media queries, but not for HighRes images.

Why do you ask for different views if Journal already does it?!

It doesn't matter if it is a standard feature or not or LiteSpeed or Apache or whatever, but it is not a must have feature, so you could use it, but you don't must. Basically Retina display is not made for HighRes images. It increases screen resolution for better reading of text, so you don't...