Search results

  1. R

    Client never gets server response

    Hi and thanks mistwang! I finally got my Rails app working properly on Litespeed! Thanks alot for the good support! Laurent
  2. R

    Client never gets server response

    Thanks for your hint mistwang! I installed version 3.0.3 and figured the source of the problem: I'm using some 'puts' statements to log some of the things in my code and they are directly redirected and taken as header thus creating monstruous headers for the response sometimes. Whilst I...
  3. R

    Client never gets server response

    2007-04-19 18:22:09.108 [DEBUG] Failed to execute 'mpstat' command: No such file or directory 2007-04-19 18:22:14.107 [DEBUG] Failed to execute 'mpstat' command: No such file or directory 2007-04-19 18:22:19.108 [DEBUG] Failed to execute 'mpstat' command: No such file or directory 2007-04-19...
  4. R

    Client never gets server response

    So in the debug log, the only I get this: 2007-04-19 18:21:58.320 [DEBUG] [128.178.83.29:2105-7#railsapp] New request: Method=[POST], URI=[/route/search], QueryString=[] Content Length=80 2007-04-19 18:21:58.320 [DEBUG] [128.178.83.29:2105-7#railsapp] Read Request Body...
  5. R

    Client never gets server response

    Sorry, debug does work and I'm looking into it...
  6. R

    Client never gets server response

    Hi, Thanks for your advice. I've set both of these timeouts to 600secs which should be plenty. For some reason I can't see any entries in the access log and neither in the error log even with debug level to high. What do you mean by 'Make sure to leave enough headroom. ' ? Thanks...
  7. R

    Client never gets server response

    Hi, I have setup a Rails app using AJAX and I am experiencing a strange behavior: I am using a form_remote_tag to post data and execute some fairly heavy calculation (about 10-30sec) on the server side. My browser only shows the action while executing the query but never gets the results back...
  8. R

    Setting Litespeed up on port 80

    ok, so one listener but 2 mappings....makes alot of sense actually!
  9. R

    Setting Litespeed up on port 80

    amazing! It does work! Thanks! :)
  10. R

    Setting Litespeed up on port 80

    My bad, I apparently wrongly copied the listener part from my file...sorry... <listenerList> <listener> <name>Default</name> <address>rrg.epfl.ch:80</address> <secure>0</secure> <vhostMapList> <vhostMap> <vhost>routerank</vhost>...
  11. R

    Setting Litespeed up on port 80

    thanks for your help... I've tried what you proposed but to be honest I'm fairly unsure of each step I'm taking. So the result is that I can reach my rails app but not the console. I get an error at server startup: 2007-04-18 18:47:41.766 [ERROR] HttpListener::start(): Can't listen at...
  12. R

    Setting Litespeed up on port 80

    Ok, or I could, as you propose if understand you right setup a Litespeed proxy to access the admin console. But anyway I'd have to prefix either the admin or the rails app address somehow, right?
  13. R

    Setting Litespeed up on port 80

    well...I'm having some troubles... so what I've done so far is: - Setup admin console port to 80 - Created a virtualhost with my rails app on port 8088 - Created an Apache Proxy to access the rails app My problem, is that I'd need to somehow prefix all addresses from my webapp. The Apache...
  14. R

    Setting Litespeed up on port 80

    Thanks for your answers! About using the port 443 for the admin console My problem is I would like to keep my apache running in parallel for comparison purpose (at least for now) and I only have 2 ports I can reach (80, 443). I am going to try to prefix all my website dirs ans setup a...
  15. R

    Setting Litespeed up on port 80

    Hi all! I've just installed Litespeed on ports 8088 / 7080 and realized my firewall policy only lets port 80 open. Since it is an institution policy I cannot change it and therefore have to configure Litespeed to use port 80. Now, I can't access the admin page since I can only ssh to the...
Top