WebSocket WebSocket wildcard host errors

[jonthn]

Note that by filing an issue, you agree that you have read and agreed to
our contribution guidelines.

NNG & Platform details.

nng-1.1.1, Debian GNU/Linux 9.5 (Stretch)

Expected Behavior

When listening to ws://*:45454/foobar I would expect that :

1. nng_dial to ws://localhost:45454/foobar works
2. that this listen does on both IPv4 and IPv6 on localhost, and the same for external/LAN interface

The documentation, indeed seems to explain it's dependent of the underlying system but as I think it's a common setup for many OS, and that it works out-of-the-box on macOS, i'm wondering if I'm missing something.

To listen to all ports on the system, the host name may be elided from the URL on the listener. This will wind up listening to all interfaces on the system, with possible caveats for IPv4 and IPv6 depending on what the underlying system supports. (On most modern systems it will map to the special IPv6 address ::, and both IPv4 and IPv6 connections will be permitted, with IPv4 addresses mapped to IPv6 addresses.)

Actual Behavior

What happens is the listen is done only on IPv4 and the dial is using IPv6.

1. Is there a way to specify that you only want IPv4 or IPv6 ?
2. As IPv6 is now the preferred protocol and I would prefer a more transparent approach, is there something that can be done to avoid specifying/limit the IP protocol version ?
3. It's an almost stock installation of Debian 9 but maybe the setup is incorrect and some configuration should be done ?

[gdamore]

This seems like a request to support to ws4:// and ws6:// to get explicit binding like we have for TCP.

The problem with not specifying an address (using INADDR_ANY) is that the consequences of this are highly unportable. This probably does an AF_INET6 binding, and expects that the platform does a dual stack mapping (IPv4 mapped IPv6 address), but the support for this is hardly universal.

Btw, what "localhost" maps to is also highly platform specific. It usually maps to 127.0.0.1, but it might also map to ::1. Or it might not.

I would be willing to contemplate adding explicit binding options (ws4:// and ws://6, as well as the wss4:// and wss6:// options) for websocket. This would require enhancing the HTTP framework somewhat to support this as well.

To be completely honest, I think when binding you're best bet is to specify an actual host IP address or name. This is actually super important if you use TLS because we need the name to match to the certificate.

[janjaapbos]

Sometimes you want to use a hostname for TLS that is different from what you want to bind to on IP.

…

On Mon, 18 Feb 2019, 08:07 gdamore, ***@***.***> wrote: This seems like a request to support to ws4:// and ws6:// to get explicit binding like we have for TCP. The problem with not specifying an address (using INADDR_ANY) is that the consequences of this are highly unportable. This probably does an AF_INET6 binding, and expects that the platform does a dual stack mapping (IPv4 mapped IPv6 address), but the support for this is hardly universal. Btw, what "localhost" maps to is also highly platform specific. It *usually* maps to 127.0.0.1, but it might *also* map to ::1. Or it might not. I would be willing to contemplate adding explicit binding options (ws4:// and ws://6, as well as the wss4:// and wss6:// options) for websocket. This would require enhancing the HTTP framework somewhat to support this as well. To be completely honest, I think when binding you're best bet is to specify an actual host IP address or name. This is actually super important if you use TLS because we need the name to match to the certificate. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#844 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBICB_IVLI9dx4B4F5Dx8zotWrIn9Oeks5vOlFMgaJpZM4ZmkQP> .

[gdamore]

Fair point @janjaapbos

[gdamore]

It is possible to specify that different hostname via the nng_tls_config_* API, btw. It just takes extra effort.