If using xhr-polling and a browser closes a tab or window, the disconnectSync in the socket.io-client method is called which sends an XHR request to the server indicating a disconnect. This line would cause that to be ignored and so the server would have to wait for a timeout to mark them as disconnect. This was possibly because it was sent from a different tcp socket than the current connection.
…environments where Object, Function, etc. have been extended. http://yuiblog.com/blog/2006/09/26/for-in-intrigue/
…used in environments that extend Object, etc." This reverts commit 81552c1.
…environments that extend Object, etc. http://yuiblog.com/blog/2006/09/26/for-in-intrigue/
…SSL that terminated at a load balancer. The shorthand logic that was here was nice and compact but didn't seem to work. Took the "intent" of the short hand and made it a bit more verbose and now it works.
…eners This fixes node v0.7.x. The node commits that broke this old behavior is here: joyent/node@78dc13f^...928ea56
…ng instead of UNDEFINED (which would throw an error on the origin.match(/^https/) below