Inconsistent axios error behavior in bun

ShlomoCode commented 1 year ago

What version of Bun is running?

1.0.2+37edd5a6e389265738e89265bcbdf2999cb81a49

What platform is your computer?

Darwin 22.6.0 arm64 arm

What steps can reproduce the bug?

Install the axios library
run this code:
```
const axios = require('axios');
```

(async () => { const urls = [ 'https://www.microsoft.com/404', // server returns html with 404 status code. error is AxiosError 'https://eastus.stt.speech.microsoft.com' // server returns only 404 status code. error is ERR_TLS_CERT_ALTNAME_INVALID ];

for (const url of urls) {
    try {
        await axios.get(url);
    } catch (error) {
        console.error(url, error.name, error.message);
    }
}

})();



### What is the expected behavior?

The error should come from axios when the request fails

### What do you see instead?

In node.js both errors come from axios and they are "AxiosError Request faile with status code 404"
**In bun**, the error in the second address, which does not return an answer but only an error code status, an error is received "`ERR_TLS_CERT_ALTNAME_INVALID fetch() failed. For more information, pass `verbose: true` in the second argument to fetch()`"

### Additional information

https://github.com/oven-sh/bun/assets/78599753/6e89bc74-8c42-4bd7-87fb-3d5e76accc44

I would be happy to provide any additional details needed