Search results

FEI, the next release will have it fixed.

Hi @LiteCache, I'm not fully sure I understand the issue you're referring to. Are you saying that the LSCWP built-in crawler is sending an incorrect "vary" header for mobile+webp when crawling the site? Would it be possible for you to open an issue on the LSCWP GitHub so others can follow the...

@rahulsoni should be available now, please confirm.

Thanks for the report, I can reproduce it too, and will forward the issue to the dev. (y)

For LSCache WordPress-related questions, please use the official WordPress support forum to report any issues. Thank you. See you at the LSCache for the WordPress support forum!

Thanks for the report, I will forward it to the team. You can ignore the warning for now since I don't see any update is needed. You might still see the same message after running the `dnf upgrade`.

Hi @rahulsoni lsphp83-redis and lsphp83-imagick for aarch64 should be available, can you give it a try? If lsphp81 is a must, let me know, I will try to fill it up when get a chance.

In my personal opinion, I don't think enabling ZTS helps.

@Akrobs Could you help verify if "mjs = text/javascript" works too?

Sounds great! Perhaps we can include it as the default supported MIME type in a future release.

Glad to know it works!

No problem, let me know if it works.

You can also try to post in this thread and see if anyone can help you.

Could you submit the issue to support@litespeedtech.com with this link appended? It might be quicker to check the issue directly.

To add the new file type support, you can try to append "mjs = application/javascript" to the /usr/local/lsws/conf/mime.properties config file, then restart the web server.

Create another static context using exp: to match the desired XML files, ensure it has a higher priority, and it should work.

What if you create a static context for phpmyadmin? Will it trigger the ream first, then process the proxy rewrite rules? https://docs.litespeedtech.com/cloud/images/wordpress/#how-do-i-secure-phpmyadmin -> method 3

Do you have any chroot or cage set for the OpenLiteSpeed? Maybe you can share more details of 503 error logs.

Hi, The "pakcageLen < 0" message indicates that there was communication error between LSWS and PHP. This is likely a PHP code issue that takes forever to run and eventually web server decided to cancel the request. If you have a robust method to reproduce it, please raise a ticket to...

I will help to bring it to their attention.