Search results

Did you upgrade from command line or via the web admin interface? There might be something wrong with the later, please try a manual upgrade then restart the server.

A DA How-to will be posted later, basically, you can follow the cPanel howto, and patch a few things in the end. Please check out http://www.litespeedtech.com/support/forum/showthread.php?t=901

Oops! looks like the shared library of libjpeg slipped in when we build the PHP binary. Will be fixed, you can fix it by installing libjpeg for now.

No, the install script will not change your existing configuration.

you can try /tv/$1? for the <location>.

LiteSpeed Web Server 3.0 has been released. Download LSWS: http://www.litespeedtech.com/products/webserver/download/ Changelog for LiteSpeed Web Server 3.0: Completely revamped web admin console: Streamlined layout, improved configuration parsing and processing to handle 1000+ virtual...

That's the current behavior of default 3xx pages, will be addressed when we add a server side include page support.

vhosts through templates still need to be fixed.

Should have been fixed in 3.0 release. You can try the 3.0 release by change the version number in the download link. It should be the 3.0 final release. Maybe the fix is only for the Apache vhosts, we will address this issue later. You can safely ignore this problem now.

Yes, the fix will go into 2.3 release.

Please try the following patch to ruby-lsapi-2.2, open file ext/lsapi/lsruby.c, in function: static VALUE lsapi_reopen( int argc, VALUE *argv, VALUE self) replace: return rb_io_reopen( argc, argv, orig_stderr ); with return rb_funcall( orig_stderr, rb_intern( "reopen" ), 2...

What's your OS and Ruby version?

No, when a backend server closes the connection in the middle of a request, like when you proxy to backend apache. There is another environment variable control idle children processes, LSAPI_MAX_IDLE_CHILDREN, please check the README file.

You can safely ignore those messages, those are produced by idle children ruby processes being killed. More children processes could be started by parent process if there is no child process can handle the new request timely. The real limit is 2 times the configured value. "Premature end of...

Thanks for the write up. :) If you don't mind, I will post it on our Wiki.

Please enable debug logging by setting "Debug Level" to "HIGH", and check which directory was referenced.

I think need to use rewrite rule or using a redirect context.

With the easy rails setup, just define a Rails context with URI "/1levelfolder/" pointing to the root directory of RoR application. Actually, just change the URI from "/" to "/1levelfoler/" for your current rails context.

You can follow our step by step setup, it will allow you set RAILS_ENV to any value you like.

To block direct access to a directory, just add a rewrite rule at vhost level like RewriteCond %{REQUEST_URI} ^/blocked/uri/ RewriteRule ^/blocked/uri/ - [R=403,F] REQUEST_URI is the same as the current URI when accessing the file directly, however, when a request was...