Search results

  1. M

    403 Forbidden error

    Access to WEB-INF directory is blocked internally by LSWS for security reason. I think it is less desirable to expose the configuration file and other servlet class objects. For anything need to be accessed directly via HTTP should be stored out side of that directory. I strongly suggest that...
  2. M

    random 404 on mod_rewrite

    We will skip 3.1.2 and release 3.2 soon, that's just for some one need a fix for the 404 problem.
  3. M

    Segfaults - protection errors

    Please update to the latest release, install GDB, set administrator's email from the web console. A crash report will be sent to you with some debug information. Please forward that email to bug @ .... .
  4. M

    EULA related information

    If you are not in porn site hosting business, you should not worry about it. Only hard-core porn site is not allowed, no matter it is legal or illegal. We certain don't want them to be able to cut any cost related to hosting by using our product. If you we found any one violate this, we will...
  5. M

    PHP - 503 error

    You can also try eAccelerator or XCache.
  6. M

    Best configuration for DDoS protection?

    Please take a look at http://www.litespeedtech.com/library/howto/#qa_dos first
  7. M

    cgi-bin directory listing

    This will be addressed in the official 3.2 release.
  8. M

    random 404 on mod_rewrite

    Please update to 3.1.2 for the fix.
  9. M

    Segfaults - protection errors

    It might be a bug in lshttpd. Do you got core dumps? What kind of OS it is? Linux or something else?
  10. M

    Trying to use litespeed load balancer for balancing lsapi

    You still need a load balancer in front proxying requests to backend nodes. Just like what you would do with a mongrel_cluster.
  11. M

    Multiviews support

    Yes, absolutely.
  12. M

    Multiviews support

    Please try a simple rewrite rule in .htaccess to rewrite the rule from foo to foo.php for you. RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_URI}.php -f RewriteRule ^(.*)$ $1.php
  13. M

    Trying to use litespeed load balancer for balancing lsapi

    For a cluster setup, we still recommend running LiteSpeed + rubylsapi on each backend node, because LSWS can manage the ruby process very well and be able serve static content or page cache really fast. You can try LSLB + ruby lsapi setup, you need to create dispatch.lsapi for the rails...
  14. M

    litespeed + ruby + rails/tmp/session issue.

    Looks like you are not running the rails application in suEXEC mode, so you got the permission problem. In suEXEC mode, ruby process starts on behalf of the owner of the rails application, it can write to tmp/sessions directory, it gives you better security as well. Highly recommended...
  15. M

    Setting index options from cPanel or .htaccess not working

    Please checkout our cPanel Wiki for work around for the directory indexing problem. It is a issue with PHP "open_basedir" configuration. -FancyIndexing will be supported later.
  16. M

    LiteSpeed VPS Edition

    Of course not. :)
  17. M

    503 errors with lsws 3.1 + rails

    Please try setting "Max Conns" to 1, if it works, the problem might be the socket connection established during Rails framework initialization, you should close all socket connection at end of your environment.rb. Since LSAPI ruby fork children process off initialized parent process, the file...
  18. M

    Access Log Customization

    You can set custom access log format like that in Apache with Enterprise edition.
  19. M

    lsphp(5) compilation error

    You can try to locate the required header files under /usr/local/ or /usr/local/include, if they are not available you need to reinstall libxml.
  20. M

    Drupal & Apache vhost & rewrites

    The rewrite rules looks fine. Please turn on Rewrite log by set "RewriteLogLevel" for that vhost in httpd.conf, turn on debug logging might be helpful as well. lsws/logs/error.log should give you some hints on what was wrong.
Top