Search results

The rewrite rules will be slightly different when configured at vhost level, Both matching URL and target URL should be full URL, not relative URLs. It should work if you fix the URLs.

Some quick notes regarding Rails: 1. turn off persistent connection for the dispatch.fcgi, Ruby's fcgi interface does not support persistent FCGI connection. 2. Turn on .htacess support at both vhost and server level to make the rewrite rule in public/.htaccess work properly. You probably...

I debugged the response header with LiveHTTPHeaders under firefox, I got header HTTP/1.x 200 OK Server: LiteSpeed Date: Wed, 08 Mar 2006 17:46:34 GMT Content-Length: 2455 Other headers were missing, like "Content-Type" and "Transfer-Encoding". Maybe you were not using the latest...

Server level configuration is 'N/A', which disables .htaccess for the whole server. it must be turned on at server level in order to enable .htacess for any vhost.

You can turn on debug logging by setting "debug level" to "high" and "log level" to "debug", activity on .htaccess should be in the log file. Remember to restart the server after the configuration changes. Maybe the directives in the .htaccess that you expect to work are not supported by...

That's correct, instead of "/var/www/webadv", "/webdav/" should be used as the the context URI I believe.

Answers to your questions: 1. No, you can install LSWS wherever you want, /usr/local/lsws or /opt/lsws is recommended location. 2. LSWS can watch and automatically reload httpd.conf if you let LSWS to use Apache's httpd.conf directly. LSWS is mod_rewrite compatible and has same...

It does not happen to me, clear your browser cache and try again. or try it with different browser.

Looks like php script handler has not been set properly, you can try another simple php script. And you need to clear your browser cache as well.

That's strange. They should behave exactly the same. Can you please post the debug logging when the server level web server application is used?

Yes, leave it on to give you the best FCGI performance.

That's because the location where 413 was detected. Move to another location, so it will be fixed in release 2.1.12 .

If you don't mind, please send us a sample apache configuration file generated by Cpanel, containing at least the working vhost and one not working vhost. You can send it bug@litespeedtech.com, We will have it fixed in next release.

That's strange, If LSWS receives some thing like Status: 302\n Location: /images/logo.gif\n \n LSWS will do external redirect. If status is absent, LSWS will do internal redirect. Just like Apache. maybe the status line is below Location or absent. Can you post the reply header, with...

You have to use the same version of php, and same opcode cache when you compare performance of two server. And same php.ini should be used. LSWS std has slightly better PHP performance than apache 1.3 in our lab environment.

Is the redirect from a script or with server configuration. You should create a redirect context if you want to do it with server configuration. An example: URI /redirectme External Redirect Yes Status Code 302 Found Destination URI /index.html

Spent a little time to investigate this issue. Found that it is true Apache can serve large static file a little faster (upto about 30%) than properly configured lsws std. The reason is Apache uses sendfile() for static file, lsws std just use plain read() or MMAP() + writev(), which is...

Actually, current lsws will generate the same traffic log as mod_log_bytes does when lsws is configured to uses cpanel managed httpd.conf Apache configuration file directly. So it is cpanel compatible, traffic logging wise.

You have set the concurrency level too high, should not over 300 for standard edition. And the concurrency level should always be lower than number of requests. And you cn increase the "Max MMAP File Size" under the tuning tab higher than the size of the test file in order to get the best...

User3, You are using a wrong "ab" parameter for the test, "-c" is for concurrrency, not for number of requests, "-n" is for that purpose. Noticed that "Complete requests" is "1" in all of your tests. :P You should use "ab -n <#req> -c <#concurrency> ...". Another tip for testing on...