Having a warning about non-zero http client timeout is useful, but it should be a documentation-level warning not an actual error. With the current implementation it's not possible to use the same http client for both standard http requests and websocket events, even when a context with timeout is provided during dialing.

Related to: #67