I have made some progress on this. I am running my rails apps as a mongrel cluster behind an apache server with an Apache reverse proxy set up. This has been just fine until very recently.
If I go directly to the mongrel server via http://localhost:8001 everything is fine. It is when I go to the apache "public" URL that my pages do not render. Apparently apache is setting the Content-Type to text/plain and this instructs the browser to not render the html. It turns out that rails does not set the Content-Type header at all, and Apache feels it just must do something. I have attempted to use a before_filter in my application controler to allow me to set headers['Content-Type'] in my application, but to no avail. Rails still is not sending any Content-Type header at all (which is perplexing and annoying). At least now I understand what is wrong, and now either have to figure out how to bully rails into sending a text/html Content-Type header or convince Apache to set this for the proxied pages. Any suggestions will be immediately put to the test. -- Tom Trebisky MMT Observatory University of Arizona -- Tucson [email protected] -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
