SSL shouldn't default to port 443

[ngnathan]

Describe the bug:
When I am connecting using a milvus client, if I set SSL to false, it still attempts to connect on port 443, as opposed to a default port for HTTP of 19530.

I would've thought that setting the SSL parameter would change the port, and it took a while to debug that it was still trying to connect on port 443.

const milvusClient = new MilvusClient({ address: "http://hosted-milvus-instance.example.com", ssl: false, username: 'user', password: 'pass' });

Workaround: Set port directly in the address.

const milvusClient = new MilvusClient({ address: "http://hosted-milvus-instance.example.com:19530", username: 'user', password: 'pass' });

Note: If this is not the intended behaviour of the SSL flag, then that's okay. Just took a while to debug that it was still connecting by default on port 443.

Steps to reproduce:

1. Set up instance of milvus.

2. Use nextjs example of milvus node sdk. https://github.com/milvus-io/milvus-sdk-node/tree/main/examples/nextjs

3. Set up address / credentials

4. Error:
   `
   Error: 4 DEADLINE_EXCEEDED: Deadline exceeded after 15.007s,name resolution: 0.010s,metadata filters: 0.001s,LB pick: 0.004s,remote_addr=<ip_address>:443

   at (Error: 4 DEADLINE_EXCEEDED: Deadline exceeded after 15.007s,name resolution: 0.010s,metadata filters: 0.001s,LB pick: 0.004s,remote_addr=<ip_address>:443)

   at new Promise ()

   at Generator.next () {

code: 4,

details: 'Deadline exceeded after 15.007s,name resolution: 0.010s,metadata filters: 0.001s,LB pick: 0.004s,remote_addr=<ip_address>:443',

metadata: [Metadata]

}

`

Milvus-node-sdk version:
"@zilliz/milvus2-sdk-node": "^2.5.6",

Milvus version:
Milvus 2.5.5

[shanghaikid]

The error is generated by the node grpc package, not the sdk self. Do you have any proxy in front of the milvus server?

In the sdk code, it enables TLS connection only if:

1. the address starts with https:// or
2. the ssl flag is true

nothing relates to the port.

[shanghaikid]

Milvus serves on the port 19530 , if you use http://hosted-milvus-instance.example.com as the address, I guess some proxy must be set in front of the milvus server.