Search results

Theoretically, in-process communication should be faster than inter-process communication. I think the reason why litespeed is faster is because it is highly optimized, and apache's inter-module communication is not that efficient. The result is similar with higher concurrency. LiteSpeed...

Thank you for your praise. Hotllink protection is on our to do list, should be ready within next 2 major releases. Mistwang

Ok, it is fixed, thank you for pointing it out. I suppose it should be generated dynamically. :-) I guess you mean "AddDefaultCharset". Ok, we can add this feature in future release. We just fixed a bug that could cause trouble for busy site, if you interested, you can try the new...

Please tell me more about this, I want to have this issue addressed. lshttpd should rotate the log file automatically when the size limit is reached, it failed to do so? Or you set the size limit bigger than 2G? Or there is no enough disk space left? Next release will allow you to add that...

Fed, Thank you for trying our product. Are you testing the standard edition? Looks like TCP port 7080 is still occupied by another process. Before you try to start the server again, make sure all "lshttpd" processes are gone. Do "ps -ef | grep lshttpd", kill all processes listed, use...

We think it is not appropriate to ignore or to create the directory automatically (may not have the permission), it should be resolved manually. Can you please send your question to info@litespeedtech.com. Thanks.

Thank you for trying our product and your feed back. Yes, it is on our to do list. Throttling is going to be at IP level, virtual host level or both. And each virtual host could has its own qouta for IP throttling. It will not be a problem after virtual host level thottling is implemented...

You are welcome and thank you for your praise. If any suggestion, please let us know. Thanks.

Thanks Your umask must be set to something like 027, this problem will be addressed in next release. Thanks.

The default installation use seperate access log file for "example" virtual host at "lsws/DEFAULT/logs/access.log", if the access log configuration is changed to "use server log", then lsws/logs/access.log will be populated. Can you please give more details about the "htdocs files" problem...

add Fast CGI context Thank you for trying our product. You need to define a FastCGI "External App" at either server level or virtual host level first, then add a "Fast CGI" context with "URI"=>"/rollcall/", "Fast CGI app"=>"your fast cgi responder". Please take a look at...

1.2.2 Please try 1.2.2.

oops! It is a bug in the AJPv13 interface introduced in 1.2, sending the whole URL including query string, but only URI without query string is expected by tomcat. The fix will be in 1.2.2. it will be released soon.

try 1.2.1 Please download and try V1.2.1, let us know the result. Thanks!

Can't reproduce the extension problem I just tried it on 1.2.1 with a fresh Tomcat install, the source code is displayed properly. 1.1 should be the same and I could not think of any thing would cause that. If you still experience that problem with the upcoming 1.2.1, can you please send us...

Any help to promote our product is welcome, but I am not sure what you are asking for? Depend on the content about your website, (we don't want to sponsor adult web site), we can offer the following if it is clearly stated on your web that it is powered by LiteSpeed: To help you...

Since we released our web server to public in July, we have been questioned for a couple times: "Why the web site is still powered by Apache?" The reason is that we thought the traffic to our web site will be very low at the beginning, so we hosted web site at http://www.p4host.com with a...

Thanks for the suggestion. Will do. We are working hard to make the transition from Apache to LiteSpeed easier. More apache compatible modules and a migratiion tool will be available soon. :-) Best Regards, LiteSpeed Team.

Thank you for the update and suggestion. :-) PHP 4.3.3 has problem when PATH_INFO is popluated. The PHP_SELF is set to PATH_INFO instead of SCRIPT_NAME. We submitted bug report but it is not resolved completely since 4.3.2. Also 4.3.2 and above should be configured with...

Cool! I compiled MMCache successfully too this time. It is nice to have another option for PHP acceleration. Thank you for your information. If you have any comments, suggestions or criticism, please let us know. Best regards, Mistwang