0.3a3 chat example is broken in a certain situation after upgrading from 0.3a2

[drosen0]

I haven't yet looked into this, nor have I checked other Firefox versions, but at least the new project chat example doesn't work in Firefox 11 beta.

Update: issue is unrelated to Firefox.

[socketstream-owen]

Ah ok. Interesting. I've tested it with Firefox 10 (latest stable release) and it works fine.

Guessing it could be a Socket.IO issue but I can't find any previous reports of this.

Is it working fine for you in another browser/version?

[drosen0]

Never mind, it's working now with no changes. The only difference since yesterday was I restarted node app. I think the issue was unrelated to Firefox. Here's what I did:

1. Another socketstream 0.3a2 app I have been playing with was already loaded in the browser at localhost:3000.

2. Quit the running 0.3a2 node app.

3. Created a new 0.3a3 chat example.

4. Start node app on the new 0.3a3 chat example.

5. Hit refresh in Firefox.

6. Typing something + Enter logged only:

   rpc: x demo.sendMessage
   

   (but not all newMessage).

7. Open Chrome to localhost:3000.

8. Typing something + Enter correctly logged:

   rpc: x demo.sendMessage
   all newMessage
   

9. Subsequent refreshing and restarting Firefox did not fix the issue.

10. Restart node app.

11. Refresh in Firefox.

12. Now it works correctly.

Perhaps a cached version of the client script registered itself incorrectly with the server? Interesting that the server didn't recover from it in this case.

[drosen0]

I just read your response to Dirk Dressel's question in the group, and realize this might be the cookie expiration issue.

[raila]

I had to delete old cookies first to get it to work.

[socketstream-owen]

Yup this is the session id cookie bug which is now fixed in the latest master. Sorry for the very stupid mistake on my part here.