Jason Su <[email protected]> wrote: > I don't think it worked, but here's the output: > > {"X-Runtime"=>"174", "Content-Type"=>"text/html", > "Content-Length"=>"1", "Set-Cookie"=>"first=; domain=.test.com; > path=/; expires=Thu, 01-Jan-1970 00:00:00 GMTsecond=1; > domain=.test.com; path=/; expires=Mon, 21-Jun-2021 01:22:23 > GMT\n_test_session=ef56a1c675e576bd0b922acb0027ebde; domain=.test.com; ^-- this is suspicous, the _test_session= cookie *is* set correctly...
> path=/; HttpOnly", "Cache-Control"=>"no-cache"} > > Here is how the response header looks: > > Set-Cookie:first=; domain=.test.com; path=/; expires=Thu, 01-Jan-1970 > 00:00:00 GMTsecond=1; domain=.test.com; path=/; expires=Mon, > 21-Jun-2021 01:32:26 GMT And you got a second Set-Cookie: line with "_test_session" in there, right? Any chance you could upgrade Rails to 2.3.11? Some rails commits since 2.3.8 look interesting: e0eb8e9c65ededce64169948d4dd51b0079cdd10 85b6d79d8a17fdef667770e31b44ac6647f8b584 -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
