Search results

"Dump the URL" means that write the URL to the log file or somewhere. I need to get an idea about how the URL looks like, and it will be even better if you can log the whole redirect response sent back to LSWS by Rails.

Maybe the redirect URL is mis-formated under LiteSpeed LSAPI, there are subtle differences in request paramters that Rails received between LiteSpeed LSAPI and webrick. Run the app under Litespeed and dump the URL.

What is your "max connection" setting? which version of LSAPI has been installed? Is that possible for me to login and take a look at the server?

Configuration looks good if the vhost is not configured to "use server config". Is .htaccess support turned on? any rewrite rule configured at vhost level or in .htaccess? Otherwise, turn on debug logging and post the detail debug log output here.

RedirectMatch will be working well in our 2.2.1 release.

OK, I see. That's pretty strange that other system usually complain about missing 32bit libraries. You need to install the 32bit compatible library, ia32-libs and ia32-libs-dev to run 32bit application on 64bit Linux. Our 32bit binary works well. :)

That's pretty strange. Must be something wrong with your OS. Is "/opt" on a dedicated partition, maybe the execution is not allow for that partition. Maybe you should try installing lsws under /usr/local instead.

Maybe there is a bug in lswsctrl, which changes to another directory. OK. please just do sudo ./lshttpd :)

Please try cd /opt/lsws/bin sudo ./lswsctrl start

It is not likely a LSWS bug, as SSL transport layer has nothing to do with 304 support. As I knew, some browsers do not cache any content received under SSL, some browsers do. Tried those URLs under firefox with "Live HTTP headers" add-on, 304 has been returned.

Only reverse proxy, no caching yet.

Please check lsws/logs/error.log and lsws/logs/stderr.log, shoud be some clue there. My guess is the process limit has been set too low.

The other user confirmed that the new RailsRunner.rb fixed the problem. Have you restart LSWS after the change? or do "killall ruby" to make sure the new RailsRunner.rb has been picked up?

Thanks for the update. That's great! We will release 2.2.1 with the fixed RailsRunner.rb on Monday. :cool:

Are you using our esay rails configuration? any customization on configuration at LSWS side? It does looks like the leading '/' is missing for some reason, but I simply cannot reproduce it here, I made the routing change. Can you create a simple testapp on that server to verify the problem? Is...

That's strange, we could not reproduce it in our lab. What's your Rails release? How is the rails application configured? Any rewrite rule involved? What is the value of 'ENV[REQUEST_URI]'?

RedirectMatch dirctive has not been supported in .htaccess, please use RedirectPermanent directive in this case. We will add RedirectMatch support soon.

Server level Outbound Bandwidth limit must be none-Zero, that's the main switch for bandwidth throttling, each vhost can have its own limit if set. http://www.litespeedtech.com/docs/webserver/config/security/#outBandwidth

I figured it is the same problem as yours. http://www.litespeedtech.com/support/forum/showthread.php?p=2727 Please try the fix I came up with and let me know the result. Thanks!

That's probably because LSAPI fork children processes off a parent process with Rails framework initialized, if a DB connection has been established during framework initialization, the connection pool in children processes will be messed up. The solution is to close all established DB...