nodester/nodester — Issue #304: Strange websocket issues
Author: akavlie
Created: 2012-02-11 20:27:32+00:00
State: open

Just sent this to Chris via email, but this is probably a better place for it:

I just put Subway (successor to web-irc) up on Nodester the other day (subway.nodester.com). I'm getting some weird problems that may (or may not) be websockets related... have you seen anything like this?

If you put in a valid IRC server, things seem to be OK. If you don't, the IRC backend sends an error event over socket.io, which works perfectly in local development.

On Nodester however, when I put in a gibberish server name, I get this in my console:

`GET http://subway.nodester.com/assets/images/loading.gif 503 (Service Unavailable)`
`GET http://subway.nodester.com/socket.io/1/?t=1328936483638 503 (Service Unavailable)`

Furthermore, I'm seeing something else weird on connection... the registration event isn't sending back the arguments it should be.

I just tried running with node 0.4.9 locally via nvm, with the same module versions as I have on nodester, and I can't reproduce the issue.

This is what I'm using to connect to socket.io from the client:

`io.connect(null, {port: PORT})`

where `PORT` is 80 in production.