Hi, > Hi Gregor, I had a similar problem once before. It seemed to happen when > the JS which started a WS connection was only in a static HTML file. It > seemed that the session wasn't started, and the session cookie consequently > wasn't sent, until the browser had actually accessed a CB controller URL. > So I made an empty controller that was served from / and included the HTML > for the page in its template rather than in a static HTML file, and from > then on the websocket handler received a SessionID. Maybe that'll work for > you too.
thank you, I'll look in that way ... > > Cheers, > Igor -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/20140611103457.GC28331%40evilAtWork.net. For more options, visit https://groups.google.com/d/optout.
