Search results

It is obvious why you get 404 File not found [/srv/www/vhosts/womenscult.com/httpdocs/category/shopping-fashion] You need to create a rewrite rule to redirect the request to the php script which supposes to handle all requests to URI "/category/...". That's the suggestion we can give based on...

If the 404 error page is generated in PHP, then it might be the problem you mentioned, if the 404 error page is LSWS' default error page, the php script has not been reached at all. Turn on debug logging by set "Debug Level" to "HIGH" under "Server"->"log" tab, you should be able to get some...

The .htaccess file does not have any rewrite rule to rewrite '/category/...' to a php script. Is this part of vBSEO? should it be handled by "vbseo.php"? The last rewrite rule for vBSEO should do it. RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.+)$...

Thanks the update, we will update our wiki.

I think 404 error is because LSWS cannot find a proper handler script for this URL. I guess file $DOC_ROOT/category/news does not exist on your server, request of http://www.site.com/category/news should be rewritten to a php script. Please show me the rewrite rule, or the URL to the target php...

The error will go away if you restart the server again.

You need to do the same for listener *:80

Is it a VPS? You need to change the admin listener from *:7080 to <your_ip>:7080 the first thing after installation.

LSAPI_MAX_IDLE is for children processes forked from the parent. you also need to check "Max idle time" configuration under "server"->"ruby" tab.

This is caused by a bug in our rewrite engine, will be fixed in 3.0.2. As a temp fix, you can try replacing "REQUEST_URI" with "CURRENT_URI", which is LiteSpeed specific rewrite variable. 3.0.2 will be available soon.

Those warnings has been fixed in upcoming 3.0.2 release. can be safely ignored now. Thanks for reporting this issue. :)

Those rewrite rules are suppose to work exactly as they were with Apache. Please give me a example, what is the input URL, what is the rewriten URL exepected? If it is a rewrite engine compatibility issue, we will fix it. Another thing could help is to enable rewrite logging, then check...

I think it is mostly likely due to the "Memory Soft/Hard Limit" set for the ruby process. You can try increase the limit under "Server"->"Ruby" and "Server"->"Security". Also, double check what environment variable is required for the JVM, and add them to the "Ruby" environment.

Yeah, the documentation need some improvements. We are looking to hire a good technical writer for this kind of job. Hopeful, we will find one soon. :)

Yeah, just do a clean reinstall and follow our Easy Rails howto http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails_easy

If the rewrite rule is configured at vhost level, the matching URL incudes the leading '/', if the rewrite is configured at context or .htaccess level, the leading '/' is part of the "RewriteBase" which is removed from the matching URL. So, you should change your rewrite rule to RewriteRule...

You can do it with addType application/x-httpd-php5 php in "Apache style configuration"

MIME type "application/x-httpd-php5" will be added when a script handler for ".php5" has been defined, so it does not have direct relationship with an external app. When you override the MIME type of any file extension to "application/x-httpd-php5", that file extension will be processed with...

David, Thank you for your praise and support! We are honored. :)

Plase check your error.log, your context configuration may not go through at server startup time. It works on our test server with a 3.0.1 installation.