You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:2399511) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
at Object.connect (_tls_wrap.js:1619:15)
at Object.tlsConnect [as createConnection] (node_modules/ws/lib/websocket.js:673:14)
at new ClientRequest (_http_client.js:312:33)
at request (https.js:312:10)
at get (https.js:316:15)
at initAsClient (node_modules/ws/lib/websocket.js:538:31)
at new WebSocket (node_modules/ws/lib/websocket.js:72:7)
at Object.<anonymous> (bug.js:2:12)
at Module._compile (internal/modules/cjs/loader.js:1075:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1096:10)
Expected result:
No deprecation warning from using wss urls to IP addresses.
Actual result:
ws erroneously set the servername TLS option to an IP address. Compare what ws does vs what node does. Node does not set the servername option if the host is an IP address while ws does.
The text was updated successfully, but these errors were encountered:
Hornwitser
changed the title
DeprecationWarning when connection to IP address over wss.
DeprecationWarning when connection to IP address over wss
Dec 28, 2020
issue.
Description
Connecting to IP addresses over wss causes a deprecation warning to emitted.
Reproducible in:
Steps to reproduce:
Connect to a WebSocket endpoint over a wss url to an IP address:
Observer node print a Deprecation warning:
Expected result:
No deprecation warning from using wss urls to IP addresses.
Actual result:
ws erroneously set the servername TLS option to an IP address. Compare what ws does vs what node does. Node does not set the servername option if the host is an IP address while ws does.
The text was updated successfully, but these errors were encountered: