Allow http/https urls for connect function

[alex-kattathra-johnson]

We currently throw an error here for everything that isn't wss or ws. Would be nice if we could allow http and https which could be upgraded into websocket at handshake.

[agalakhov]

This would be contrary to the RFC definition.

[3](https://www.rfc-editor.org/rfc/rfc6455.html#section-3).  WebSocket URIs

   This specification defines two URI schemes, using the ABNF syntax
   defined in [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234) [[RFC5234](https://www.rfc-editor.org/rfc/rfc5234)], and terminology and ABNF productions
   defined by the URI specification [RFC 3986](https://www.rfc-editor.org/rfc/rfc3986) [[RFC3986](https://www.rfc-editor.org/rfc/rfc3986)].

          ws-URI = "ws:" "//" host [ ":" port ] path [ "?" query ]
          wss-URI = "wss:" "//" host [ ":" port ] path [ "?" query ]

          host = <host, defined in [[RFC3986], Section 3.2.2](https://www.rfc-editor.org/rfc/rfc3986#section-3.2.2)>
          port = <port, defined in [[RFC3986], Section 3.2.3](https://www.rfc-editor.org/rfc/rfc3986#section-3.2.3)>
          path = <path-abempty, defined in [[RFC3986], Section 3.3](https://www.rfc-editor.org/rfc/rfc3986#section-3.3)>
          query = <query, defined in [[RFC3986], Section 3.4](https://www.rfc-editor.org/rfc/rfc3986#section-3.4)>

   The port component is OPTIONAL; the default for "ws" is port 80,
   while the default for "wss" is port 443.

[alex-kattathra-johnson]

Please check discussion in #451