litespeedtech / litespeedtech/openlitespeed
noabort and noconntimeout don't seem to work for wp-cron
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 233
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
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=#`
```
RewriteEngine On
RewriteRule (wp-cron|backupbuddy|importbuddy)\.php - [E=noabort:1, E=noconntimeout:1]
```
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked LiteSpeed troubleshooting page and the .htaccess directives shown in the report. Reproduce the behavior for wp-cron, backupbuddy, or importbuddy using both RewriteRule and SetEnvIf, then determine whether noabort and noconntimeout differ between OpenLiteSpeed and LiteSpeed Enterprise; done means documenting or fixing the supported configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100