I suspect this is a litespeed bug. Take the following Ruby on Rails code in my view:
In Windows/Webrick, when on the /status/main page, this returns the expected:
Request: /status/main
Current?: /status/main
But on my Redhat (ES 3) server, running Litespeed 2.2 Std, that same code produces:
Request: status/main
Current?: /status/main
note the missing slash returned by request_uri
Since this works on other web servers, I suspect its a mistake in how Litespeed is responding to Rails. This crucially needs to be fixed, as it causes various Rails functions to fail, such as current_page? and, more importantly, link_to_unless_current
I'm currently evaluating this for a corporate product and I've been very impressed with Litespeed 2.2's Rails support. Performance blows away other Rails servers so far... good job!
thanks
Code:
[FONT="Courier New"][COLOR="Blue"]Request: <%= @controller.request.request_uri %><br/>
Current?: <%= CGI.escapeHTML(url_for({ :controller => '/status', :action => 'main' })) %>[/COLOR][/FONT]
Request: /status/main
Current?: /status/main
But on my Redhat (ES 3) server, running Litespeed 2.2 Std, that same code produces:
Request: status/main
Current?: /status/main
note the missing slash returned by request_uri
Since this works on other web servers, I suspect its a mistake in how Litespeed is responding to Rails. This crucially needs to be fixed, as it causes various Rails functions to fail, such as current_page? and, more importantly, link_to_unless_current
I'm currently evaluating this for a corporate product and I've been very impressed with Litespeed 2.2's Rails support. Performance blows away other Rails servers so far... good job!
thanks
Last edited: