bind EINVAL on valid IPv6 Address (IPv4 works fine!)

[yoyo00xx]

• Version: 15.12.0
• Platform: 5.8.0-45-generic Nominating Chris Dickinson to the TC #51-Ubuntu SMP Fri Feb 19 13:24:51 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
• Subsystem: https, ws, http

What steps will reproduce the bug?

1. Use the https library and bind an IPv6 localaddress

How often does it reproduce? Is there a required condition?

Can be reproduced with the usage of any IPv6 address in the interface

What is the expected behavior?

I am supposed to be able to make the request without any problems just like when binding an IPv4

What do you see instead?

bind EINVAL error

Additional information

I have tested with multiple IPv4 addresses in the interface and they all worked but non of the IPv6 are working

This is the code:

`const https = require('https');
(async () => {
const options = {
//Not real site
hostname: 'example.com',
path: '/test',
localAddress:'Ipv6 address'
}
https.get(options,(res) => {
let body = "";

    res.on("data", (chunk) => {
        body += chunk;
    });

    res.on("end", () => {
        try {
            let json = JSON.parse(body);
            console.log(json)
            // do something with JSON
        } catch (error) {
            console.error(error.message);
        };
    });

}).on("error", (error) => {
    console.error(error.message);
});

})();`

[yoyo00xx]

I know exactly what is the issue. nodejs https library is not smart enough to know that it is dealing with IPv6. I tried to make a udp4 socket by providing an IPv6 address and got the same error above, when I used udp6 it created it fine and binded.

So suggestion: Introduce explicit parameters to say an address is ipv6 OR make it smarter to determine if the address is IPv6

[yoyo00xx]

OK for future people needing to fix this issue.

Provide this option in the http/https "family: 6"

Example:

const options = { hostname: 'example.com', family: 6, //<- This is the option headers: { 'Your headers here' }, localAddress:"Your IPv6 Address here }