Thanks for the report.

I fixed this with a slightly different patch. http/https are now not permitted for WebSocket URIs.

Note one potential problem:

        if (port == -1) {
            if ("ws".equalsIgnoreCase(scheme)) {
                sa = new InetSocketAddress(host, 80);
            } else {
                // TODO HTTPS support
                // sa = new InetSocketAddress(host, 443);
                throw new DeploymentException("TODO: HTTPS");
            }
        } else {
            sa = new InetSocketAddress(host, port);
        }

Now, I understand that SSL support is not complete yet, but as-written this won't allow customization of the port when connecting via SSL (wss). It is imperative that this be allowed (consider port 8443 as an example). Suggestion:

        if ("ws".equalsIgnoreCase(scheme)) {
            if (port == -1) {
                port = 80;
            }
            sa = new InetSocketAddress(host, port);
        } else {
            if (port == -1) {
                port = 443;
            }
            // TODO HTTPS support
            // sa = new InetSocketAddress(host, port);
            throw new DeploymentException("TODO: HTTPS");
        }

Of course, you may be planning on doing that anyway when you complete SSL support.

(In reply to comment #2)
> Note one potential problem:

I must be being blind. What is the problem here?

If SSL support is completed by commenting out:

sa = new InetSocketAddress(host, 443);

Then if someone specifies a URL:

wss://localhost:8443/webSocketEndpoint

The code will attempt to connect to this instead:

wss://localhost:443/webSocketEndpoint

Scratch that previous comment. I was the one that was blind. Your code will work fine.