Search results

  1. B

    Litespeed 3.2 error starting

    That worked, I knew I was forgetting something. Thanks
  2. B

    Litespeed 3.2 error starting

    I think I may know what it is, I'm running 64 bit linux but may not have the 32 bit bindings installed. I'll try install those and running Litespeed.
  3. B

    Litespeed 3.2 error starting

    I just tried that and I get permission denied even if run by the root.
  4. B

    Litespeed 3.2 error starting

    I tried installing litepseed 3.2 on a fresh linux system. At the end of the install when it tried to start it failed. I got the error: Cannot find /opt/lsws/bin/lshttpd I checked and the file is there, I tried rebooting and reinstalling with no luck.. Any ideas, the older version worked fine...
  5. B

    3.1 Linux 64 problem

    I just tried upgrading to the new 3.1 and I'm getting an error on startup. *** glibc detected *** free(): invalid pointer: 0x0000000000797900 *** /opt/lsws/bin/lswsctrl: line 37: 17614 Aborted ./$EXECUTABLE [ERROR] Failed to start lshttpd! Thanks, Dan
  6. B

    twitter.com

    I ran liveheaders in firefox on the site and the main content reads Server: Joynet Web, but everything else says including the images reads Server: Litespeed. I think they are having some database and ruby growing pains.
  7. B

    twitter.com

    It looks like twitter.com is now running their Ruby on Rails site with Litespeed web server. They are probably the largest traffic RoR site on the web, so it will interesting to see how it scales. I was wondering if there entire website was hosted from one Litespeed web server. I believe...
  8. B

    Rails caching with cookies

    Wow, that was fast thanks for the amazing support. I'm in the trial period for the 64-bit linux ent version. We plan on purchasing the ent. edition when were ready to launch the site. Thanks again.
  9. B

    Rails caching with cookies

    Here is some info on the Safari caching bug. http://bugs.webkit.org/show_bug.cgi?id=13128
  10. B

    Rails caching with cookies

    I'm not sure this is a bug, but if you put more then one line the Extra Headers field in the Rail context menu, Litespeed fails to restart or startup. One line seems to work fine.
  11. B

    Rails caching with cookies

    Ok the headers seems to work fine in Firefox. However, I was testing with Safari and I just read in Google that Safari ignores caches headers within HTML. Can I try adding the headers to the extra headers field in the Rails context section of Litespeed?
  12. B

    Rails caching with cookies

    Well I played around with LiveHeaders and you were rite the page is being cached by the browser. I tried adding the no-cache headers to my default rails layout page and it didn't seem to fix the problem. When I notice the problem the page does not refresh and the the browser doesn't even...
  13. B

    Rails caching with cookies

    That was also my first idea. I disabled cache completely within my browser and tried a no-cache header, also tried a few different browsers. I also double checked that the cookie is removed upon logout. Does everything look fine in my RewriteCond? I've been trying to figure out this little...
  14. B

    Rails caching with cookies

    I'm trying to implement cookie based conditional page caching for a rails project. Very similar to this site: http://www.ethelred.org/articles/2006/10/22/conditional-use-of-page-cache-in-rails Basically non-logged in users get a cached site and logged in users get dynamic content. I have...
Top