On Jun 16, 2010, at 9:48 AM, Evgeny Morozov wrote: > Thanks. > > You are right, the only "cosign" cookie somehow disappears from headers.
Your browser is never sending it. Here's what your Live HTTP header capture shows me: (C => client; S => Server) C: GET /cosign-bin/cosign.cgi HTTP/1.1 S: 200, Set-Cookie: cosign=...; path=/; secure C: POST /cosign/cosign.cgi HTTP/1.1 C: Cookie: exposedFactors=,friend S: 200 (with the "Cookies required" html page) Notice that the POST from your browser doesn't include the cosign=<value> cookie the server returned. For some reason, your browser isn't saving the cookie. I'm not sure why, but it certainly looks like a browser issue, not a cosign problem. andrew ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
