Open nickchomey opened 3 hours ago
I see that there's apparently already noabort mechanism specifically for wp-cron here. But it doesnt seem to do anything. Perhaps it needs to be noconntimeout
instead?
I now see these in the error log
2024-12-01 22:45:39.448661 [INFO] [41258] Rewrite directive: <IfModule Litespeed> bypassed.
2024-12-01 22:45:39.448665 [INFO] [41258] Invalid rewrite directive: SetEnvIf Request_URI "(wp-cron|backupbuddy|importbuddy|inf)\.php" noabort noconntimeout
2024-12-01 22:45:39.448667 [INFO] [41258] Rewrite directive: </IfModule> bypassed.
Same if I use SetEnv. So, i guess those are only LSE.
But even if I just put the rewrite outside of the <IfModule Litespeed>
tag, it still doesnt work
Hi there, i have this at the very top of my site's .htaccess file, but it doesnt seem to be overriding
env LSAPI_MAX_PROCESS_TIME=#
Nor does it work if I swap the RewriteRule with
SetEnvIf Request_URI "(wp-cron|backupbuddy|importbuddy)\.php" noabort noconntimeout
Why might this be? The troubleshooting on this page says this should work. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:run-without-timeouts#troubleshooting
Does it only work for litespeed enterprise?