socket.setTimeout is ignored after HTTP upgrade

[hanzi]

I did a basic WebSocket implementation on my own, which involves upgrading a HTTP connection. Node seems to set up a 2 minute idle timeout for these connections, which I guess is the default behavior for HTTP connections.

My connections can be idle for quite some time, so I wanted to disable this timeout. I tried

`````` socket.setTimeout(0);```
but that's totally getting ignored. The 'socket' object is fine -- immediately after this line I appended a listener for the 'timeout' event to it (for debugging purposes) and that worked.

Even more, not only does the 'timeout' event fire, it also closes the connection. I can prevent this by doing
socket.removeAllListeners('timeout');
but that's just a workaround.

Is this a bug or am I doing something wrong? Is there another way to disable that timeout?

(The 'socket' object is the one I received from the 'upgrade' event of the HTTP server.)

[bnoordhuis]

Do you have a test case I can try? It seems to work for me and I don't see anything in lib/net.js or lib/http.js that could cause it to fail. By the way, with what version of Node are you seeing this behaviour?

[jameshartig]

Running:
https://gist.github.com/1422141

Generated:
/usr/local/bin/node testTimeout.js
setTimeout(0) failed. Timed out!
setTimeout(0) worked correctly 2nd time.

[jameshartig]

Ignore 8fb848c. I originally though that would fix it but it caused issues.