This project is archived and is in readonly mode.
Session-Cookie appearing in content
-
Tobsch
See the attached image...
-
David Smalley
I am also seeing this issue, will investigate
-
David Smalley
I wasn't able to precisely pin down at what point the Set-Cookie line gets added into the body. I was able to fix the issue by switching to the :active_record_store instead of using the cookie sessions.
It seems the issue only appears in cookie based sessions and only if you start setting extra cookies.
In my case I am using an old version of the restful_authentication plugin and it is only if the remember_me cookie is set that the session cookie gets printed into the body.
e.g. cookies[:auth_token] = { :value => self.current_user.remember_token , :expires => self.current_user.remember_token_expires_at }
Then the Set-Cookie line appears in the body of the page, but only contains the session cookie.
Checking headers in Firebug the "Cookie:" header contains both the auth_token and the session cookie.
Will continue to investigate...
-
thedarkone
Upgrade to Passenger 2.1, it should be fixed there.
-
Richard Poirier
Same problem here. Anywhere I was setting a cookie in the app now puts it in the body of the response. This is with Passenger 2.0.6. It doesn't happen on mongrel.
-
richy zhang
I have such a problem with Passenger 2.0.6 too. However, after Passenger is upgraded to 2.1.1, the problem disappears. This version of passenger is still in beta, so you can't get it from rubyforge. You may take a look at their blog(http://blog.phusion.nl/2009/03/0...>
-
James Chen
Same problem here. Upgrading to Passenger 2.1.1(beta) solved the problem.
-
Pratik
- Assigned user set to Pratik
- State changed from new to invalid
Hongli confirmed upgrading to passenger 2.1.1 solves the problem.
Thanks.
