When doing some experiments to try to find out I was unable to explicitly set
the Content-Type by fiddling with the headers array, I took at look at the
file /u1/rails/my_app/log/mongrel.8000.log and I see lots of error tracebacks
from mongrel that ultimately come from a mongrel routine "send_cookies".
Some google searches on this error message leads me to the following discussion
on a site called "stackoverflow" that describes exactly the behavior I have
been seeing.
http://stackoverflow.com/questions/2911852/problems-running-ruby-on-rails-apps-on-shared-hosted-server
These discussions link to the following proposed fix, which I am pondering.
https://rails.lighthouseapp.com/projects/8994/tickets/4690
As they describe it, mongrel crashes when trying to put cookies
in the response header, the resulting HTTP header is incomplete
(missing Content-Type), i.e. exactly the problem I am seeing.
So this is a bug in mongrel 1.1.5 that has been causing trouble since
at least May of this year. I wonder if some official fix is in place yet.
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.
--
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.
