Clients hangs when trying to connect to a URL that is not NATS

Malformed URL throws exception but if you accidentally enter an URL that is valid but not nats-server the call hangs.

Steps to reproduce:

var cf = new ConnectionFactory();
var opts = ConnectionFactory.GetDefaultOptions()
opt.Servers = new[] {a valid URL to a web server e.g. http://localhost}
try
{
   var conn = cf.CreateConnection(opts)
}
catch(Exception ex)
{
   // Some Action
}

Actual Result: Code hangs no exception thrown. Expected Result: Exception thrown

[per-ove]

@danielwertheim About other improvement. For our use case we see no need for such an option. And if we can trust the handshake to report errors we are very satisfied.

[ColinSullivan1]

I think there’s value in throwing an exception on an invalid protocol - it’d help users more quickly identify a problem. We could accept nats://, tls:// (which sets up a secure connection, like go), and just empty that defaults to nats://. It shouldn’t break any existing deployments.