I've been testing out 2.3.1, and I've noticed this weird bug I'm kind of stumped about. Of course I've been using script/server locally, but I've noticed that a Set-Cookie header keeps appearing at the very top of the response body, above the HTML and everything. It seems to happen whenever there are multiple cookies being set -- I ran a request through Live HTTP Headers and it looks like a Set-Cookie header is properly sent for the first cookie but if there are any other cookies, they come through above the response body as I mentioned.
I know someone's encountered this before, because I found #195 in Lighthouse[1], but the fix that Josh made [2] doesn't seem to have helped here -- I think because he fixed the deprecated FCGI handler, but not necessarily Mongrel or anything like that. I can confirm that when using Thin instead of Mongrel, the rogue headers no longer show up in the response body. The thing is, I haven't seen talk about this problem other than in Lighthouse. So what I'm wondering now is if this is a problem with Mongrel, or with Rack's Mongrel handler, or with Rails...? Anybody got any ideas? -- Elliot [1]: http://rails.lighthouseapp.com/projects/8994/tickets/1957-sessions-break-in-23-with-mongrel [2]: http://github.com/rails/rails/commit/b6e56efe07cb3c2e999216f995403aa9206226a2 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
