Hi, I recently tried to setup an application using WebSocket behind pound only to find out that the WebSocket functionality was not working. Whenever a WebSocket message is received, pound writes a "e414 headers: request URI too long" message to syslog. Looking at the pound source code, this seems to be because pound searches for EOL in the message (in get_headers,strip_eol) which it can't find and thus writes an error to syslog and drops the message instead of forwarding the message to the backend.
While pound has no problem passing the HTTP 101 protocol upgrade messages around, it fails with the subsequent WebSocket messages. Would the pound developers find it desirable to have support for WebSocket messages after the required HTTP handshake in pound? Do you see any obvious blocker for such a feature? Would you accept a patch implementing it? If yes, how would you like it to be implemented? cheers, josch -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
