Search results

If you proxy to Apache, doesn't that mean Apache needs to handle the PHP request? For general OLS, you can set the handler via the web admin. See https://docs.openlitespeed.org/configuration#set-up-script-handlers-at-the-server-level for more information.

Hi, it seems you have multiple full-page systems enabled at the same time, this may be the reason. Please choose only one cache system at a time.

Sure, because OpenLiteSpeed supports only rewrite rules in .htaccess file, whereas, LSWS supports all rules. See editions: https://www.litespeedtech.com/products/litespeed-web-server/editions

Hi, 116734 process does not exist from your shared output. You might want to kill the 39880 instead.

You can inbox me or submit the issue to support@litespeedtech.com with the post link appended.

Hi @Clive Loseby For WordPress LSCache plugin-related questions, please post on the LSCache for WordPress support forum! Thank you.

It won't cause issues as long as you have the correct cert set on the virtual host level.

It applies to the External App only, if all VH/websites use this external app, then yes, it applies to all websites.

It will be released in the next few days. If you want to try the binary, you could use the following command to upgrade it. /usr/local/lsws/admin/misc/lsup.sh -v 1.7.19

I tried the same settings, and the PHP env variable works in my test. Added "X_DMC_USR=11111" to the environment. Test script <?php foreach($_SERVER as $key => $value){ echo "<b>$key:</b> $value<br>\n"; } Browser displays X_DMC_USR: 11111 PATH: /bin:/usr/bin HTTP_ACCEPT:...

Maybe your post has a special string or char, please try to use a code block, maybe it will work.

No problem.

For LS Enterprise version, you can apply ExpiresByType on the .htaccess file.

Hi, For WordPress Plugin questions, please post on the LSCache for WordPress support forum, thanks.

It will be released in the next few days. If you want to try the binary, you could use the following command to upgrade it. /usr/local/lsws/admin/misc/lsup.sh -v 1.7.19

Because OLS v1.7.19 package is not ready yet, if you want to try the binary, you could use the following command to upgrade it. /usr/local/lsws/admin/misc/lsup.sh -v 1.7.19

Because it is returned by the Quic Cloud server, not from the origin server. If you bypass the CDN, then you should see the difference.

For openlitespeed, the browser cache is controlled by the server, please go to openlitespeed web console > Server Configuration > General > Expires Settings and add type from there.

I see, then you might want to contact DA support for more details about the CB changes.

What if you filter 'REQUEST_SCHEME' only to the /usr/local/directadmin/data/users/*