https.get, TLS, *node*, *async*, and perhaps others and EPROTO type 40 error

[Martii]

Trying the direct approach since I got maintainer having a bad day over at nodejs/help#1098

• 8.9.4 and 9.5.0:
• Linux (multiple distros):
• Scope (install, code, runtime, meta, other?):
• Module https://www.npmjs.com/package/request (and version of 2.83.0) (relevant when converted from node internal https.get and produces similar output ):

Basically the .on('error', ... isn't happening when using https.request, http.get, and request from the url at https://confluence.bredex.de/images/icons/profilepics/default.png

Clearly the server is misconfigured but it trips our production and development environment.

What am I doing incorrectly? This routine works for properly configured servers just not that server.

The simple request at https://github.com/OpenUserJS/OpenUserJS.org/pull/1324/files#diff-b755ddbc6b2edf964c5586d742e3afdaL1459
The data stream at https://github.com/OpenUserJS/OpenUserJS.org/pull/1324/files#diff-b755ddbc6b2edf964c5586d742e3afdaL1461
The end stream at https://github.com/OpenUserJS/OpenUserJS.org/pull/1324/files#diff-b755ddbc6b2edf964c5586d742e3afdaL1468
The error trap at https://github.com/OpenUserJS/OpenUserJS.org/pull/1324/files#diff-b755ddbc6b2edf964c5586d742e3afdaL1488

All of this is wrapped in the async package.

Thanks so much.

[Martii]

I've been given some advice on rechecking something... please hold while I retest.

[bnoordhuis]

And also given advice on posting a minimal test case, remember? The contributing guide has more hints if you need them.

I'm closing this out because we already established the issue wasn't with node.js itself.

[Martii]

I am a contributor already @bnoordhuis (see here) . Please reopen this and refrain from being snarky. You have managed to upset me by your negative reactions now. You need to let someone else handle this and not you. Thank you for your cooperation.

[jasnell]

@Martii ... I've reopened the original issue in the help repo since your issue is still unresolved. If this does turn out to be some kind of bug in core, please come back and open an issue here. Definitely hope you manage to get the issue resolved :-)

[Martii]

@jasnell
Thank you... I'm really confused why those two test cases work but buried in async it doesn't appear to trap it. Will continue over there.