Search results

You need to add listener to vhost mapping for the rails vhost.

tried LSWS 3.3.15 and tomcat 6 on a iBook G4, it works.

You should set "Update Offset" to different value for vhosts to avoid start awstats update for all sites at the same time. Create a few similar vhost templates instead of only one.

no plan for that.

We probably will add a flat text file for template member configuration in addition to the current configuration.

The index.html problem is caused by the rewrite rules under the rails context. add a rewrite rule RewriteRule ^examples - [L] should fix it.

You can do that with manual configuration http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails The rail context just automates most steps.

Just tried tomcat 6 with LSWS, works fine.

looks like your servlet engine has not been configured properly, so LiteSpeed denies any request handled by it. Please check lsws/logs/error.log for related errors, and turn debug logging should help. For "http://www.myhost.com/examples/" return 404 problem, you need to add "index.html" as one...

That is not a LiteSpeed bug, the behavior is as designed and follow that of Apache, the rails context does some magic behind the scene to make rails configuration as simple as possible, but it may not work perfectly for all situations. In your case, you may have to use rewrite rule to fix it up...

Another possible solution is to add a rewrite rule to rails context to rewrite url "/v1/groups.atom" to "/v1/v1/groups.atom" if file "/trunk/rails1/public/v1/groups.atom" exists.

Can you make it cache the result to /trunk/rails1/public/groups.atom instead of /trunk/rails1/public/v1/groups.atom? Since /trunk/rails1/public/ is mapped to URL "/v1/" already, LSWS won't add "/v1" to the path again. Another possible solution is to configure the Rails app manually instead of...

If you run the app under "/v1" URL, you'd better not using it as the document root for the vhost.

This can be done with third party log watch script, not need to be in LSWS core. If you find any good solution, please let us know or update our wiki. :)

Why not just cache the result under /trunk/rails1/public/?

Should change the static gzip cache directory under "server"->"tuning" tab. By default it uses /tmp/lshttpd/swap . I recommend using "$SERVER_ROOT/cache" or any directory you want to use, just make sure the partition has enough free space.

You can try latest 3.3.16 build by changing the version number in the download link. If *.awstats was not accessed in 1800 seconds, it will be removed automatically.

No, progress bar implementation depends on SSI to pull some internal data like data received from web server. Each progress bar implementation require different data, it is going to take a while.

You need to remove that file manually. we will add an function to remove old files automatically in the new release.

That's great you have figured it out. Would you mind sharing a little bit more on how to find it out? What log file you checked? Error? What TCP parameter need to be tuned? We would like to put in our wiki to help other uses who have similar issue.