Search results

  1. E

    Ruby 1.9

    Hi mistwang, Rails 2.3.5 is compatible with Ruby 1.9. Maybe you have to apply some patches around to adapt an existent codebase, but it works well. https://changelog.com/posts/rails-2-3-5-released Would it require some other change besides working on ruby-lsapi? Thank you.
  2. E

    Restart individual virtual hosts

    I'd like to know if it's possible to support individual VH restart in the console, something like: > lswsctrl restart my-virtual-host In the web interface we can do it, in the console is a must too. I've read some threads that this is possible when using the shared server setup, but...
  3. E

    Ruby 1.9

    I'd like to know if a plan for Ruby 1.9 compatibility is on the agenda. Thanks.
  4. E

    Graceful Restarts not working

    Same issue with 3.3.2. Can you instruct me on creating a new root? How can I give the password?
  5. E

    Graceful Restarts not working

    Hi, I can't get Graceful restarts working again, even by the web console or "lswsctrl restart". I am using the last version (3.3) Enterprise Edition. All my Rails processes continue there, and when I use the web console the browser get stuck in the request. I could not find anything in...
  6. E

    Tunning very high traffic Rails site

    That's right, I will se what I can do. Thanks!
  7. E

    Tunning very high traffic Rails site

    Hi, I have a site which must be rendering about 2M page views/day, but I am not being able to achieve this yet. The first thing I did was to try the Enterprise Edition, since 150 connections was a bottleneck... now it's using about 600~700 connections. Now, Rails is the bottleneck. I am...
  8. E

    Expires header not updated when status 304

    Hi, mistwang. It works like this only to ROOT URI? Why doesn't behave this way for something like example.com/start/? Actually, I see many Rails applications being broken with this upgrade, like mine. I can't see a straightforward solution besides using a Rewrite, is this the way to go...
  9. E

    Expires header not updated when status 304

    Hi mistwang, I did what you suggesting, set DEBUG level to HIGH. I have no request filter rule configured. The difference I can see is in return code ("24" from 3.1.2 and "25" from 3.1.1). However, the only URI with this problem is "/", all other URI's work without problems. 3.1.2 2007-06-02...
  10. E

    Expires header not updated when status 304

    403 Hi mistwang, I've just upgraded a production server to this version, and the main URL of the site gets a 403, like "http://www.example.com/". The previous version was 3.1.1-std, and when I switch back it works without problem. Any idea? Thank you.
  11. E

    Expires header not updated when status 304

    Reinstall Hi mistwang, How could I reinstall this version in production smoothly? Is there a way? If I just reinstall it using the same values, like users and directories, it would be OK? I mena, it would use the same settings as before? Thanks.
  12. E

    Expires header not updated when status 304

    It works, thanks! However, I have a question. I tested with the Example virtual host, setting image expires to a short time. It worked perfectly, but I didn't get why "index.html" gets cached, do you know why? Just curious. Will it be available via update, link 3.1.1? Thanks once again.
  13. E

    Expires header not updated when status 304

    I've noticed that LSWS does not send Expires header in 304 responses, so the browser always uses the old Expires. Shouldn't the Expires be updated? Use case: 1. First page visit get /default.css response: 200, Expires: 25-May-2007 18:00 2. Page visit before expires (nothing...
Top