No way to respond to the HTTP upgrade request #3189

Closed
mmalecki opened this Issue Apr 29, 2012 · 1 comment

2 participants

@mmalecki

When there's an incoming HTTP request with Upgrade header, node intercepts it, leaving no way to respond to it like it was a regular HTTP request. WebSocket spec says to respond with meaningful HTTP codes when upgrade is not possible. There's likely an API missing (or needing to be changed) on the node side.

I realize I can just write to a socket, but it's a workaround.

@koichik

This will fix by #3036 in v0.9. Closing.

@koichik koichik closed this May 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment