Search results

Does the download link point to a PHP script or directly to the static file? If static file is streamed through PHP script, the static file will be buffered by LSWS as well, so it is not efficient at all.

Don't worry, we will have it addressed soon. Need to run some tests. Besides the file uploads, do you serve file downloads though PHP as well? PHP read the file then send it to client? If you did so, you should change it to let LSWS serve it directly via a internal redirect in PHP...

No, when buffer memory was used up in the middle of a request, this error will occur. LSWS cannot switch from buffer memory to swap memory in the middle of a request. Some area can be improved in the future. If LSWS uses all 3gb RAM for the buffer, the server will become extremely slow. So...

You don't have to. You can relocate the swap directory to somewhere else if you want. http://www.litespeedtech.com/docs/webserver/config/general/#swappingDir

Please try setting "Max I/O buffer size" to "0", yes "zero", the swapping space will be limited by available disk space under /tmp. Performance wise, you may not notice big difference unless the disk is too busy, server is disk I/O bound. Use a dedicate disk for /tmp/lshttpd will help.

LSAPI can be used as CLI PHP interpreter. I think both version should do the job. Does you script require any PEAR module? maybe you check whether required module can be found by PHP, You can try "/php5/bin/php -c path_to_php.ini /path_to_php_script" see if it works.

In theory, larger I/O buffer should be better, but I think it does not matter much what parameter you tune for such large file. TMP directory size will grow automatically as long as there are enough free space.

Yes, You do not need to. It should not have big impact on performance, and LSWS will avoid using it whenever possible. Handling upload of 650mb file via HTTP then processing with PHP is not recommended. It is not efficient with too much overhead, better use FTP for file that big. If you have a...

It depends on what license he want to use. 4-CPU or even 2-CPU license is fine for PHP/MySQL driven sites. For mainly serving HTTPS or static content, 4-CPU license is highly recommended, otherwise 2-CPU license should be good as well. We do not require the license matching the number of...

Please try "/php5/bin/php /path_to_php_script" from command line first, make sure it works.

Depends on your configuration? as many as you want.

What is URL for the 404 error page? is that <myerror404.html>? Does <myerror404.html> exist under the document root? You do not need to add a <myerror404.html> context.

Make sure to set the URL like "/my_cusotm_error_page_url" without "http:/".

It is the customer error page comes with default vhost. You should set http://www.litespeedtech.com/docs/webserver/config/vhostgeneral/#errPage properly, and make sure that when you access the URL specified there directly from browser, your custom error page shows up.

Your Rails application sent some thing before response header was sent to STDOUT, so the response header was treated as response body. LiteSpeed use 404 handler for rails application, that's why you see 404 status code, instead of 200, because "Status: 200 OK" header was treated as response...

Thanks for the update. this will be helpful to other cPanel users who run Apache behind LiteSpeed.

use Apache directive AddType application/x-httpd-php5 php for that vhost, either in httpd.conf or .htaccess.

I think there might be some output to Ruby processes' STDOUT before the first response header was sent. So, the response header was treated as part of the response body.

Since LSWS buffer the request body and forward the whole request to PHP backend all at once, it will use PHP backend more efficiently but upload progress bar does not work. We will implement the upload progress bar function internally.

What do you get if you access the custom error page directly like http://www.yourdomain.com/error404.html ?