Search results

Thank you for the suggestion. :-) We will setup a demo server pretty soon.

Thank you for the information. :-) Yes, we saw it. lighttpd is a very small web server almost as fast as litespeed. But it has no web admin interface, no throttling and connection accounting, no proxy, limited configurability, ... The implementation of its claimed features is very simple...

Thank you for the nice testimonial! I'd like to add some comments about the scalabilities of LSWS and the backend web apps. Not only LSWS itself scale very well, but also it can increase the scalability of backend web apps to the same level, by pipelining request sequentially through limited...

Yes, there are more interests in LDAP authentication. We will priorities it. :-)

I am probably wrong on my solution suggested as the fast cgi context with regular expression may not populate SCRIPT_FILENAME, nor PATH_INFO and PATH_TRANSLATED. You may have to place the whole "safedir/" out side the directory tree contains all php scripts.

Thanks, we will increase the default limit.

You are welcome. :-) Would you mind share the result in the feedback forum? :wink: LSWS does not support client certification yet. it is on our to do list with low priority, as it is not a highly demonded feature. We will evaluate how much work is involved and prioritize it. Absolutely!

There is no easy solution right now. We will add a similiar feature like that in the upcoming release. :-) You need to remove php script handler at server level, define a general context with regular rexporession like "exp:^/safedir/", and a fast cgi context with regular expression like...

The behavior of LSWS you observed is correct and as designed. We are not sure it is standard or not, I think it make sense this way. As a context handler, web server does not know exactly the URL points to a script file or not, so only PATH_TRANSLATED is set. Glad you found the solution...

You probably run a lot of other processes with user that lsws is running as, you need to go to server "security" tab, change the process limit in "CGI Resource Limits" table, either increase the limit or set it to "0" to disable it. Let me know whether it works.

Yes, just Apache's htpasswd to generate the password file for now. You will be able to manage htpasswd file from our web admin interface pretty soon. :-) George

mod_cache is not implemented yet, it is on our to do list though. Thank you for the feed back. George

Yes, litespeed web server will use the system default limit if it is set to 0. Have fun. :-)

Are you running other daemon server like Apache with user name webserver? You need to increase the resouce limit for CGI from web admin interface, under server's "security" tab, set "Process Soft/Hard Limit" to higher than the total number of processes running as "webserver".

The previous result might be cached by the browser, just restart the web server, do a no-cache refresh from your browser (press "shift" or "ctrl" key) when you click the refresh button. Should work now.

Looks like some thing wrong with the CGI written in shell scipt. Please try the CGI script on command line as "root" user and the user who the web server process is running as. cd lsws/DEFAULT/cgi-bin/ ./helloworld sudo -u <username> ./helloworld I think the last command will fail and...

That's normal, for technical reason. When you start another instance of lshttpd, the running processes will be reused. If you preter to stop them, just run command "killall admin_php", "killall php". This issue might be solved in the future release. Best regards, George

I could not think of any thing that could cause helloworld script stop working. Please turn on the debug log by changing "Debug level" to "high", and check lsws/logs/error.log or just use the log viewer, see if you can figure some thing out. Please send the debug log to bug@litespeedtech.com...

Thank you for trying our product. looks like your /dev/sda7 is full, make sure there are enough free space left. Make sure the user who the web server running as can write to /tmp/.

Some thing wrong with your PHP binary, maybe module conflictions, check the core file with gdb see if you can figure some thing out. There are two "--with-config-file-path" parameters in your configuration. I suggest You compile php with basic configuration,parameters, make sure it works...