What is the significance of the Cobalt cookie "bhResults"?

Andrew Gerber

I see the cookie `bhResults` being set for Cobalt sessions. I'm wondering, what is the significance of this cookie? For whatever reason, sometimes it seems this cookie doesn't get encoded properly when routing a specific module to my local machine, causing subsequent calls to other modules (say, UDS) to fail.

If I remove the cookie value completely or manually encode the value, everything works fine. What is the role of this cookie and any idea why I would only see this cookie when routing from deployed Website to my local module, but not the other way around?

Andrew Gerber

`bhResults` and any other cookie beginning with `bh` are set by BrowserHawk when accessing the Cobalt sign-on page. These cookies can be ignored/omitted when making module to module calls.