- Version: v8.17.0, v10.23.1, v12.20.1, v14.15.4, v15.5.1
- Platform: Darwin imac.local 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64
- Subsystem: http
What steps will reproduce the bug?
$ cat test.js
const http = require('http');
const req = http.get('http://[2604:1380:45f1:3f00::1]:4002');
req.on('error', console.error);
req.abort();
$ node test.js
node:events:353
throw er; // Unhandled 'error' event
^
Error: connect EHOSTUNREACH 2604:1380:45f1:3f00::1:4002 - Local (:::49474)
at internalConnect (node:net:910:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:430:12)
at node:net:1001:9
at processTicksAndRejections (node:internal/process/task_queues:75:11)
Emitted 'error' event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:80:21) {
errno: -65,
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '2604:1380:45f1:3f00::1',
port: 4002
}
How often does it reproduce? Is there a required condition?
Always. No required condition.
What is the expected behavior?
The error is handled by the 'error' event listener.
What do you see instead?
The error is not handled.
Additional information
If req.abort() is removed the error is correctly handled.
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always. No required condition.
What is the expected behavior?
The error is handled by the
'error'event listener.What do you see instead?
The error is not handled.
Additional information
If
req.abort()is removed the error is correctly handled.