Hello all. I am hoping this is some simple thing that you can help me with. A few years ago I put together a couple of rails applications, and they have been running nicely -- until I just did an upgrade of the server they run on. They still run on the upgraded server (but not in a way that is of any use). What happens now is that any view gets rendered as verbatim HTML, the browser does not process any of the HTML!! I am running rails 2.3.5 (or so it tells me) and have no clue what version I was running prior to the upgrade -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
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 tom-Hj0cqe6WdgQ@public.gmane.org -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 3:40 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote:> 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 ...How are you determining that? I can see (using Firebug) a content-type header on any response from a standard mongrel-based app here, e.g. Content-Type text/html; charset=utf-8 -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 04:00:11PM -0700, Hassan Schroeder wrote:> On Wed, Jul 21, 2010 at 3:40 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote: > > > 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 ... > > How are you determining that? I can see (using Firebug) a content-type > header on any response from a standard mongrel-based app here, e.g. > > Content-Type text/html; charset=utf-8I use "telnet localhost 8001" then type "GET / HTTP/1.1" followed by two returns and then I get the server response. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 4:27 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote:> I use "telnet localhost 8001" then type "GET / HTTP/1.1" followed > by two returns and then I get the server response.I''d suggest using Firebug for a more realistic environment (sending Accept headers, etc. with the request) but regardless -- $ telnet localhost 3000 Trying ::1... telnet: connect to address ::1: Connection refused Trying fe80::1... telnet: connect to address fe80::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is ''^]''. GET / HTTP/1.1 HTTP/1.1 200 OK Connection: close Date: Wed, 21 Jul 2010 23:37:29 GMT Last-Modified: Mon, 31 May 2010 15:05:02 GMT Content-Type: text/html Content-Length: 7625 .... What version of Ruby and Mongrel are you using? -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 04:42:24PM -0700, Hassan Schroeder wrote:> I''d suggest using Firebug for a more realistic environment (sending > Accept headers, etc. with the request) but regardless --> What version of Ruby and Mongrel are you using?Ruby is version 1.8.6 Rails is 2.3.5 However, this application was built long ago, probably with rails 1.2.3 and may be inheriting old behaviors. The only rails now installed on my server though is 2.3.5 The headers I get from my old application are as follows: (/u1/tom) cholla $ telnet localhost 8001 Trying 127.0.0.1... Connected to localhost. Escape character is ''^]''. GET / HTTP/1.1 HTTP/1.1 200 OK Connection: close Date: Wed, 21 Jul 2010 23:50:52 GMT Content-Length: 1877 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" ====================================================However, when I set up a new fresh application via the following, I get the proper headers as you do: cd /u1/rails rails new cd new script/server (/u1/tom) cholla $ telnet localhost 3000 Trying 127.0.0.1... Connected to localhost. Escape character is ''^]''. GET / HTTP/1.1 HTTP/1.1 200 OK Connection: close Date: Wed, 21 Jul 2010 23:50:02 GMT Last-Modified: Wed, 21 Jul 2010 23:49:34 GMT Content-Type: text/html Content-Length: 7466 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 04:42:24PM -0700, Hassan Schroeder wrote:> What version of Ruby and Mongrel are you using?Ruby is version 1.8.6 Rails is 2.3.5 Mongrel is 1.1.5 -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 5:00 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote:> However, this application was built long ago, probably with rails 1.2.3 > and may be inheriting old behaviors. > The only rails now installed on my server though is 2.3.5Are you absolutely sure the old version of rails isn''t in the app''s vendor directory? What''s in /vendor, /vendor/gems and /vendor/plugins ? -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 05:27:54PM -0700, Hassan Schroeder wrote:> Are you absolutely sure the old version of rails isn''t in the app''s > vendor directory?At this point, there aren''t many things I am absolutely sure of. :-)> What''s in /vendor, /vendor/gems and /vendor/plugins ?My application is at /u1/rails/micros There is a directory /u1/rails/micros/vendor The directory is empty (apart from another empty directory vendor/plugins) All my rails "stuff" is at /usr/lib/ruby/gems/1.8/gems The old rails versions used to be here also, but were deleted months ago to avoid mischief and confusion. Thanks for your help and valuable probing questions. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 6:02 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote:> At this point, there aren''t many things I am absolutely sure of. :-):-)> The old rails versions used to be here also, > but were deleted months ago to avoid mischief and confusion.Is there a line in config/environment.rb that starts with RAILS_GEM_VERSION If so, what is it? And what does `gem list --local` produce? -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 06:20:45PM -0700, Hassan Schroeder wrote:> Is there a line in config/environment.rb that starts with > RAILS_GEM_VERSION > > If so, what is it?It is commented out and looks exactly like this: #RAILS_GEM_VERSION = ''1.2.3'' unless defined? RAILS_GEM_VERSION As I remember I commented this out about a year ago when I converted from 1.2.3 to 2.3.5 or whatever 2.x.x version I converted to then. As I remembered back then I did rake rails:update at the time and this was a good thing to do then.> And what does `gem list --local` produce?(~) cholla $ gem list --local *** LOCAL GEMS *** actionmailer (2.3.5, 1.3.3) actionpack (2.3.5, 1.13.3) actionwebservice (1.2.3) activerecord (2.3.5, 1.15.3) activeresource (2.3.5) activesupport (2.3.5, 1.4.2) cgi_multipart_eof_fix (2.5.0) daemons (1.0.10) fastercsv (1.2.1) fastthread (1.0.7) gem_plugin (0.2.3) gettext (2.1.0) hpricot (0.8.2) locale (2.0.5) mislav-will_paginate (2.3.2) mongrel (1.1.5) mongrel_cluster (1.0.5) rack (1.1.0) rails (2.3.5, 1.2.3) rake (0.8.7, 0.7.3) ruby-opengl (0.60.1) sqlite3-ruby (1.2.4) zoom (0.4.1) I have this growing feeling that I need to start from scratch with 2.3.5 and hand migrate my application. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Jul 21, 2010 at 6:41 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote:> (~) cholla $ gem list --localNothing''s really jumping out at me from that list...> I have this growing feeling that I need to start from scratch > with 2.3.5 and hand migrate my application.and having been there -- yeah, that''s probably the quickest way to resolve this :-) My only suggestions: 1) If you don''t have unit tests, you might want to try running your app under the original version of Rails and write some before (re-)upgrading. My first Rails apps had none, but I''ve learned :-) 2) Version control -- git is easy, but whatever -- is a blessing. It *will* make the process much less stressful. Good luck! -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hassan Schroeder wrote:> On Wed, Jul 21, 2010 at 6:41 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> wrote: > >> (~) cholla $ gem list --local > > Nothing''s really jumping out at me from that list......except for the fact that you''ve still got the old Rails gems you claim to have deleted. Go to the root directory of your app and run script/about. What does it say? -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Thu, Jul 22, 2010 at 04:48:03AM +0200, Marnen Laibow-Koser wrote:> Hassan Schroeder wrote: > >> (~) cholla $ gem list --local > > Nothing''s really jumping out at me from that list... > > ...except for the fact that you''ve still got the old Rails gems you > claim to have deleted.Hmm, well (just guessing) I probably should have used gem itself to delete them instead of going to /usr/lib/ruby/gems/1.8/gems and doing an rm -rf on the old directories. Out of curiosity, what would have been the proper way to delete them and keep gem informed?> Go to the root directory of your app and run script/about. > What does it say?(/u1/rails/micros) cholla $ script/about About your application''s environment Ruby version 1.8.6 (x86_64-linux) RubyGems version 1.3.7 Rack version 1.1 Rails version 2.3.5 Active Record version 2.3.5 Active Resource version 2.3.5 Action Mailer version 2.3.5 Active Support version 2.3.5 Application root /u1/rails/micros Environment development Database adapter mysql Database schema version 0 -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marnen Laibow-Koser
2010-Jul-22 19:07 UTC
Re: Re: Rails views now display as verbatim HTML
Tom Trebisky wrote:> On Thu, Jul 22, 2010 at 04:48:03AM +0200, Marnen Laibow-Koser wrote: >> Hassan Schroeder wrote: >> >> (~) cholla $ gem list --local >> > Nothing''s really jumping out at me from that list... >> >> ...except for the fact that you''ve still got the old Rails gems you >> claim to have deleted. > > Hmm, well (just guessing) I probably should have used gem itself to > delete > them instead of going to /usr/lib/ruby/gems/1.8/gems and doing an rm -rf > on the old directories. Out of curiosity, what would have been the > proper way to delete them and keep gem informed?gem uninstall or gem cleanup.> >> Go to the root directory of your app and run script/about. >> What does it say? > > (/u1/rails/micros) cholla $ script/about > About your application''s environment > Ruby version 1.8.6 (x86_64-linux) > RubyGems version 1.3.7 > Rack version 1.1 > Rails version 2.3.5 > Active Record version 2.3.5 > Active Resource version 2.3.5 > Action Mailer version 2.3.5 > Active Support version 2.3.5 > Application root /u1/rails/micros > Environment development > Database adapter mysql > Database schema version 0OK, then that looks good to me. Is all that what you expected to see? Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Thu, Jul 22, 2010 at 09:07:23PM +0200, Marnen Laibow-Koser wrote:> gem uninstall or gem cleanup.Great, thanks, after gem cleanup I see: [root@cholla rails]# gem list --local *** LOCAL GEMS *** actionmailer (2.3.5) actionpack (2.3.5) actionwebservice (1.2.3) activerecord (2.3.5) activeresource (2.3.5) activesupport (2.3.5) cgi_multipart_eof_fix (2.5.0) daemons (1.0.10) fastercsv (1.2.1) fastthread (1.0.7) gem_plugin (0.2.3) gettext (2.1.0) hpricot (0.8.2) locale (2.0.5) mislav-will_paginate (2.3.2) mongrel (1.1.5) mongrel_cluster (1.0.5) rack (1.1.0) rails (2.3.5) rake (0.8.7) ruby-opengl (0.60.1) sqlite3-ruby (1.2.4) zoom (0.4.1)> >> Go to the root directory of your app and run script/about. > >> What does it say? > > > > (/u1/rails/micros) cholla $ script/about > > About your application''s environment > > Ruby version 1.8.6 (x86_64-linux) > > RubyGems version 1.3.7 > > Rack version 1.1 > > Rails version 2.3.5 > > Active Record version 2.3.5 > > Active Resource version 2.3.5 > > Action Mailer version 2.3.5 > > Active Support version 2.3.5 > > Application root /u1/rails/micros > > Environment development > > Database adapter mysql > > Database schema version 0 > > OK, then that looks good to me. Is all that what you expected to see?It looks swell to me, but I sure wish my application would run. :-> I''m gonna go play with firebug and verify this business of rails not setting the Content-Type header. Then I am going to look into why adding this bit of code to app/controllers/application_controller.rb does not force rails to emit a Content-Type header: class ApplicationController < ActionController::Base before_filter :set_content_type def set_content_type headers["Content-Type"] = "text/html; charset=utf-8" end end Once I get fed up with all that, I am probably going to throw in the towel and act as though I am starting from scratch building my application under 2.3.5, via: cd /u1/rails mv micros micros_BAD rails micros And then move files one by one from micros_BAD to micros -- all this presuming that I am inheriting something nasty in the scaffolding left over from rails 1.2.3. -- Tom Trebisky MMT Observatory University of Arizona -- Tucson tom-Hj0cqe6WdgQ@public.gmane.org -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
Hassan Schroeder
2010-Jul-22 21:43 UTC
Re: Re: Re: Rails views now display as verbatim HTML
On Thu, Jul 22, 2010 at 2:21 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> 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 ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Thu, Jul 22, 2010 at 02:43:51PM -0700, Hassan Schroeder wrote:> On Thu, Jul 22, 2010 at 2:21 PM, Tom Trebisky <tom-Hj0cqe6WdgQ@public.gmane.org> 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 :-)I''ll google on passenger in just a minute. I have my problem fixed now. What I did was to hack on the file /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/cgi.rb I added some code to the send_cookies() method, following the lead of one of the fellows posting in the forums I mentioned, (note the commented out reference to the uninitialized "options" array that was, I think, the source of the problem) --- def send_cookies(to) # convert the cookies based on the myriad of possible ways to set a cookie if @head[''cookie''] cookie = @head[''cookie''] case cookie when Array cookie.each {|c| to[''Set-Cookie''] = c.to_s } when Hash cookie.each_value {|c| to[''Set-Cookie''] = c.to_s} # TJT code added to fix nasty bug when String cookies = cookie.split.map { |a| a[-1..-1]=='';''?a[0..-2]:a } cookies.each do |c| if c.split(''='').length == 2 to[''Set-Cookie''] = c else to[''Set-Cookie''] = c+''='' end end else to[''Set-Cookie''] = cookie.to_s # TJT end of code added #else # to[''Set-Cookie''] = options[''cookie''].to_s end @head.delete(''cookie'') end # @output_cookies seems to never be used, but we''ll process it just in case @output_cookies.each {|c| to[''Set-Cookie''] = c.to_s } if @output_cookies end At this point I am happy (and maybe a little wiser) and on to other things ----- -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marnen Laibow-Koser
2010-Jul-22 22:18 UTC
Re: Re: Re: Rails views now display as verbatim HTML
Tom Trebisky wrote:> On Thu, Jul 22, 2010 at 02:43:51PM -0700, Hassan Schroeder wrote: >> `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 :-) > > I''ll google on passenger in just a minute. >Definitely the nicest way to serve Rails apps.> I have my problem fixed now. What I did was to hack on the file > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/cgi.rbGreat! May I suggest contributing your patch back to the gem maintainer, if you haven''t already done so? I''ll keep this in mind if I ever have a MIME-type issue with Mongrel. Always good to have the additional info. Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.