Turned out to be Sarafi's support of the tag being less then
perfect. I put wireshark on the connection and noticed that Safari was
prematurely terminating the connection. This (via some end of session
code in the web sever) was starting a new session, which was in turn
creating the new cookie. So
On Aug 11, 2012, at 9:56 AM, jeff robinson wrote:
> This hand off causes a change in the user agent that is
> reported to Catalyst, which in turn cause the Session to be reset.
Are you sure that's the reason? If you haven't already you may want to turn on
debugging and take a close look at your