Search results

It is recommended to do it this way as the .htaccess hack will make all html static files served as PHP scripts, it will be a big performance hit for cached pages.

Have you include the Mint java script in your rails application, I think it is the only thing required to make Mint to collect access information for a Rails application.

It is recommended to store vhost configuration file under $SERVER_ROOT/conf/. Our rails templated is highly recommended. For the application error, you can try WEBrick first, if it works well then try trouble shoot LiteSpeed.

Yes, but you don't have to, just need to find a way to add the admin password to the password file.

The configuration looks ok. You can turn on debug logging by set "Debug Level" to "HIGH" then check error.log see what is going on. Make sure to restart the server after configuration change. Another way to do it is to create a static context for Mint directory, and add the configurations you...

FileInfo and Options, and it does not hurt to check all of them. It follows the same spec mentioned in Apache/PHP documentation.

The comma should be removed, maybe a bug in 2.2.6's web admin requires that. You can fix the configuration file manually. I tried this method with 3.0.1, it works. Another solution is to use a rewrite rule to force MIME type of .php file to application/x-httpd-php5, you can give it a try as well.

It should work. Mabye htaccess support has not been enabled in your setup. Please check "Allow Override" configuration for your RoR vhost.

You can try override the MIME setting for "php" file under that context, add something in "MIME Type" like application/x-httpd-php5 php And you should have set a php5 external app as script handler for .php5 at vhost level.

Please try the updated 64bit package.

Sorry about that, we need to rebuild the binary. There must be a bug in vmware, the clock goes so fast when run solaris under it. Will let you know when it is ready.

Looks like you have to build your own lsphp binary using the mysql client library on your server. Please check out the toturial on building lsphp binary in our Wiki.

This error is pretty strange. "request validation failed" means that the MD5 checksum in the CGI request is currupted, which should not happen at all. Can you try a clean installation of 3.0.1 on your server? We failed to reproduce the problem on your test server with 64bit Solaris 10 installation.

You need to check the Mysql socket location used by PHP, you can look that information up in a phpinfo() page. The mysql socket address should match what is used by MySQL. You can fix the mysql socket address in php.ini referenced in phpinfo() page.

What do you mean Preserve Hostname? The "Host" header should contain the hostname refered in the request.

This is a new feature available in 3.0 Enterprise, x-forwarded-for header will be used as remote ip in access log if "Use Client IP in Header" is set to yes.

I think it is a PHP problem, maybe some required PHP extension has not be inclded in lsphp binary, maybe you should check the configruation options in phpinfo() with Apache, then build your own lsphp binary with similar configuration options. For more information regarding building lsphp...

It has been fixed in 3.0.1, you may need to upgrade manually from command line.

Thanks for the bug report. Those warnings will be fixed in next release, you can safely ignore those for now.

Should be very well. Yes, start lsws as root, it will change user id to the user id specified during installation, you should use the same user id as apache2 during installation. How special it is, usually, "combined" log format is used by Apache, which is the defautl format used by LSWS.