Search results

5.0.x supports SetEnvIf directives in .htaccess. If it works with Apache, it should work with litespeed.

Is the source IP in the trusted IP list?

Do not use <Directory ...> in native LSWS configuration. Use AddType directly, if you want to change it under a subdirectory, create a static context.

No. it is tested against the total number of running processes of that user at the moment fork() was called. Kernel has no clue on how many children processes is going to be started when need to start the main process.

Yes, not high enough as there are more processes running as the user that lsphp7 need to run as.

increase the process limit of lsphp5 and lsphp7 external apps.

Sounds like you are running 64bit lsphp binary from 32bit LSWS standard. you need to check stderr.log to found out why it fails. You may need to compile 32bit lsphp binary.

Yes, that's correct. because server need to start PHP process group on demand for each account. For shared hosting, it is better to run LSWS on each backend node.

There is no additional authentication except for the "PHP suEXEC Daemon mode" as the PHP main process running as root user. This mode cannot be used for remote PHP server due to that the master secret keeps changing after each server restart. Yes, firewall will be the only way to protect the...

Not likely, litespeed should work exactly the same as Apache. Need to find out what the root cause of the problem and fix it. it does not matter which web server is used.

Yes, PHP are selected through "Script Handler" configuration, so it does not matter it is local or remote, a single instance or load balanced group.

SecRule REQUEST_HEADERS:X-Forwarded-For is correct.

Need to use new mod_security syntax. SecRule RequestHeaders:X-Forworded-for pattern

It can be done at vhost level, cannot do it .htaccess, because If you need to let rewrite to handle URL pointing to existing directory, you need to do it at vhost level. "AllowNoSlash" option does not matter.

HTTP/2 has bandwidth throttling for virtual streams. It may slow down large data transfers. Please turn on debug logging for the 25MB file upload. then grep your IP to locate log entries, send the debug log messages to bug@litespeed... for analysis. It could be improved with some HTTP/2...

You can add <IfModule Litespeed> SpdyEnabled off </IfModule> to the respective SSL vhost configuration through cPanel vhost level include.

thanks for the confirmation.

It is supported in 5.1RC3 via "ctl:ruleEngine=DetectionOnly". If you want you can try it with /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.1RC3.

/usr/loca/lsws/admin/misc/lsup.sh -f -v 5.0.9 will get your latest build of 5.0.9. You need to rebuild PHP to upgrade the PHP SAPI version to V6.9

Thanks for the confirmation.