Search results

@LuigiMdg Sorry, no information what Events or Controllers are good for. This module for PrestaShop is strange and seems to be unfinished. Code and functions exist, but can't be used because other functions are missing. Anybody from LiteSpeed should either rebuild or finish it, but it also...

@dmartinez FYI: The code of the plugin has all functions to make Mobile View and some other features of the plugin work, but a function to write cache varies into .htaccess is missing, so this plugin seems to be unfinished.

Hey colleague, now I know what you want after you posted the almost complete code about image rewriting. How can we help you if you don't even tell us what software it is? If you have to pull everything out of your nose, nothing can come of it.

Your comment about @AndreyPopov in other post. :) So I use your comment because I feel like I'm talking to a wall. ;)

This means what it means. Access to requested source is forbidden, so you have any configuration that doesn't allow access to cp_errordocument.shtml, but this error comes from cPanel and not from LiteSpeed and that's maybe why you don't have any error entry in log file.

There is a conflict between cPanel and LiteSpeed and each of both said the other one did a missconfiguration. This conflict goes back to year 200*, but this error isn't a real error, but it is confusing everyone. LiteSpeed displays an error_document (403,404,500, ....) and cPanel expects this...

You have cPanel, right?

@LuigiMdg "I feel like I'm talking to a wall" said @LuigiMdg

You already have what you need. Copy & Paste your code and replace .jpg with .png. That's it.

@LuigiMdg Sorry, I should have explained my rule . It works different as yours and isn't applicable for your case, because you have different directory name for each kind of image type, so forget it. But what I meant it was to test your rule with different accept headers. curl is your friend! :)

If there is a redirection, then redirection works and if it works, then there is no error. If only redirect location is wrong, then either your rule must be wrong or request header for Accept contains values that causes the redirection. Why don't you do what I suggested?

@LuigiMdg Why do you expect any error? To proof if your rule works you only have to set different request accept header. The one with Accept/webp and the other one without. But indepently from this, LSWS is very tolerant related to wrong .htaccess rules. Depending on your HTML code turn the...

I DM you, check your inbox

Both, because a complete page can be cached and an ESI hole as well, but most of the time with different cache parameters. To understand this it requires to understand what ESI is?

Means you can use cache tags to purge the cache of everything. Want to see a demo for OpenCart?

Nevertheless, there is a method to purge cache of ESI holes, but not with curl.

https://www.google.com/search?q=configure+ssh+port

You may not open all ports, otherwise you are open for everything. This is a high security risk. Only open such ports you really need, but each port for a certain service. For SSH you must configure your system to tell your system which port is for SSH.

You need to use the right port for SSH access. Port 80 can't be the right port.

Stale cache is not a WP feature, it works native whenever LScache is running. You only have to add "~s" to tag name in purge header like X-LiteSpeed-Purge: pubtag1,pubtag2~s https://docs.litespeedtech.com/lscache/devguide/controls/#x-litespeed-purge