On Thu, Jul 22, 2010 at 2:21 PM, Tom Trebisky <[email protected]> wrote: > Both discussions above label this as a problem with rails 2.3.8, which I > think is erroneous (it looks like mongrel 1.1.5 is the culprit, buy I may > be missing the point). In any event I am seeing the problem with rails > 2.3.5 and mongrel 1.1.5 > > Indeed, when I run my app via script/server then telnet to port 3000, I do > get the proper Content-Type header, so this bug is specific to mongrel.
`script/server` will run mongrel if it's present -- the problem seems to be with the mongrel_rails cluster stuff, rather than mongrel itself. Maybe a good time to switch to Passenger :-) -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- 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.
