Search results

no, you cannot at this moment, since openssl 1.0.1 is not stable, we still use openssl 0.9.8, no TLS 1.1/1.2 support yet.

Those default "Request filter" rules should be disabled. http://www.litespeedtech.com/docs/webserver/config/reqfilter/

It is fixed with latest 4.2.3 build, just do /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.3

We are checking it now.

sure. we will add it to our to-do list.

We tested self signed SSL certificate on cPanel 11.38, it is working fine.

Please grep your mod_security rule for "Location", it is in a "SecRule ...", not in <Location ...> directive. Please give us an example, so we can analyze.

It is around the corner. :)

We will try to reproduce this issue with our internal cPanel test server. Can you please check log file see if there is any related error message? It could be the file format of the SSL certificate. maybe the fastest way to resolve this is to let us login to the server and take a look. you can...

It is not likely be changed, however, you can easily address it with a rewrite rule, by testing the PATH_INFO env with RewiteCond directive.

You need to capture phpinfo() output when apache used, then build lsphp5 with all configuration options listed in phpinfo().

Looks like %{ENV:REDIRECT_SUBDOMAIN} is not set, as it is not a standard environment variable. Just try the simplified rule. RewriteCond %{ENV:SUBDOMAIN} ="" RewriteCond %{HTTP_HOST} ^([a-z0-9][-a-z0-9]+)\.silverwayve\.com\.?(:80)?$ [NC] RewriteCond %{DOCUMENT_ROOT}/subdomains/%1 -d...

that's correct.

You have to put "CacheDisable private" in the corresponding <VirtualHost ...> configuration section of httpd.conf. private cache was processed before .htaccess.

REMOTE_ADDR has been converted to IPv4 format automatically without using the rewrite rule. SERVER_ADDR was not converted to IPv4, will fix that in 4.2.3 release.

Thanks for the bug report. fix will be in 4.2.3 release.

Yes, it is likely the case.

PHP crashed while processing this request. You could enable core dump of php process by adding environment LSAPI_ALLOW_CORE_DUMP to lsphp5 external app. http://www.litespeedtech.com/php-litespeed-sapi.html then check the core dump with gdb.

there is no good solution for high disk I/O situation like that. Any disk I/O operation in lshttpd will block the whole process, you need to move log, swap etc to memory disk if the server has spare memory. You should trouble shoot why disk I/O is so high, and reduce it as much as you can.

A simple solution is too add "Cache-control" header along with the "Location" header. so, this response wont be cached, as long as the cache policy is set to respect the response cache-control header. However, if one URL could return more than one possible results, it is not public cache...