RailsBaseURI doesn't appear to work with Rails 2.2.2 to deploy Rails sites in a subdirectory. Two forum posts - http://groups.google.com/group/phusion-passenger/browse_thread/thread/d3e7b1f524f5ab62 and http://groups.google.com/group/phusion-passenger/browse_thread/thread/bc1c7e99701ab5db - confirm this is a problem, and give a work around (config.action_controller.relative_url_root in environment.rb).

I wasn't sure if this had been reported, so thought it best to flag up here so that it could be fixed.

My system specs are included below:

Fedora 9, Ruby 1.8.6, RubyGems 1.3.1 (updated from dist 1.2.0 using update_gems), Rails 2.2.2

I have also experienced same problem on CentOS 5.2, Ruby 1.8.6-p287, RubyGems 1.3.1, and rails 2.2.2. Though my rails app works well with setting ENV['RAILS_RELATIVE_URL_ROOT'], it's very inconvenient :(.

It seems like this is probably related to this change in rails:

http://github.com/rails/rails/commit/a87462afcb6c642e59bfcd2e11e3351e2b718c38

According to the changelog, this went in in Rails 2.2.0.

Glad somebody caught this. I was beating my head into the wall with several apps not behaving. HOpe this gets fixed soon.

I also experienced this error and spent the entire day searching the web before I finally found the fix on a blog entry somewhere. Finally got it working, but it surely tripped me up for quite the long while. Thank you to all the people who DID discover a workaround/fix for the time being for posting what you found so that I could eventually find it. ;)

I'm experiencing this issue as well. Thank goodness it came up early in my searching.

Now that I've been using it, in some ways I like the fact that Rails 2.2.2 requires you to specify the prefix path for the application, because it also uses that to calculate the asset tag URLs. I'd hate for Phusion to fix the RailsBaseURI issue, but then still have all the asset tags reporting the wrong URLs.

@m3moore: That's not how it used to work. Rails would read the RAILS_RELATIVE_URL_ROOT environment variable, and ensure that your asset tag URLs were prefixed by the relative URL. Now you need to configure the relative URL twice; once in Rails and once in Passenger. That's the only difference.

I have filed a ticket in LH, to find out the reason for the change and/or whether it can be fixed on the Rails end of things:

http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1946-setting-a-relative-root-url-via-a- web-server-not-possible-anymore

I hit this issue trying to install typo. Glad there is a workaround, but I wish the workaround was listed in the passenger documentation under sub-uri documentation http://www.modrails.com/documentation/Users%20guide.html#deploying_rails_to_sub_uri

They closed the ticket at https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1946-setting-a-relative-root-url-via-a- because they consider it's a passenger issue.

Fixed in commit 5eb8c84.