Search results

Please download 2.1.15 package again, htaccess support has not been turned on for vhost configured through httpd.conf. The bug has been fixed.

Is the rewrite rule in httpd.conf or .htaccess, if it is .htaccess, you need to turn on "allow override" at server level. If you don't mind, you can send your httpd.conf to bug (at) litespeedtech.com , we will give it a try.

Looking for "Allow Override" option and "Rewrite" tab under vhost configuration.

I had contact php developer list, got reply from Rasmus as following If more users request this on php list, it will be included into the php core sooner. :)

Please use the attached script to replace lsws/admin/misc/rc-inst.sh and run it again. Oops, Problem with attaching file, trying to fix it now. All right, gave up, insert the following code in to rc-inst.sh, below 'INIT_DIR="" ' line if [ "x`uname -s`" = "xDarwin" ]; then...

One simple solution is just take out the listener to vhost mapping for that vhost and add it back later when you want to enable it.

It depends what Apache directives being used by those control panel. Current LSWS support the most commonly used Apache directives, and the supported directives will grow as time goes by. Based on my knowledge of Rails configuration in Apache, it may not be supported completely, directives...

Yeah, it depends on how it was used. Pretty handy for FastCGI that can spawn children process, but is not good for on demand dynamic spawning that LSWS is capable of .

Thanks for the information. It may not work well when you need to start multiple instances binding to the same address, may got address is already in use error. :)

Configuration for CPanel compatible bandwidth log will be available in 2.1.15

What you observed probably does not related to keepalive, just for some reason the upload stalled and the connection timed out. It is "connection timeout", not the "keepalive timeout". You can send chunk of your error log to bug [at] litespeed . com . Anyway, we have to be able to reliably...

Thank you for the bug report. To turn off keepalive, you should set "Max keepalive requests" to 0 or 1, either at server level or at vhost level. changing keepalive timeout will not work. The setenvif trick in apache does not work with LSWS. And,we don't find any real problem with using...

Only other standalone fcgi-spawner I know of is the "cgi-fcgi" from FCGI SDK. ;-) May not be anything better than fcgi-spawner. Maybe I can add an option to let LSWS start FCGI at server startup. :-)

You can let fcgi application started by LSWS using tcp instead of unix socket. but LSWS only start them on demand, so it may not be a good choice for pure fcgi spawner. :-) Actually, php-fcgi itself has an option "-b" to bind to an address. It hasnot be implemented in earlier release, but...

Yes, the extra code for LSAPI is pretty simple. You need to define a LSAPI application for each LSAPI ruby script, then mount the application via a context or script handler.

testcgi.rb itself is using LSAPI interface, it is for testing the ruby "cgi" extension under LSAPI. Itself is a LSAPI application, It will not work under the lsruby_runner.

I am not exactly sure what is the problem, maybe support for your ruby script is poor. You can try the following hello.rb, if it works, please send us your testing script, we will figure out the problem. #!/usr/local/bin/ruby print "HTTP/1.0 200 OK\r\nContent-type: text/html\r\n\r\nHello...

Please check lsws/logs/stderr.log and zend optimizer related directives in lsws/conf/php.ini.

You can only install one instance of LSWS on one server. However, you can have LSWS listen on multiple ports.

Sorry for lacking a step by step tutorial, we will add one later. I think the step you missing is to configure a mount point of the LSAPI dispatcher. You can do that by either To add a LSAPI context with URI: /dispatch.lsapi, using the LSAPI as handler. Or To add a script handler...