Don't allow half-open TLS connections #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm trying to detect clients rejecting my HTTPS certificate, using httpolyglot.
With the current httpolyglot server, if a client cleanly closes a TLS connection after the server hello (i.e. when it decides it doesn't like the certificate), the current httpolyglot never fires a
tlsClientError
event, whilsthttps.Server
does.I've hit this because that's the behaviour of Node 12 TLS clients - they cleanly close connections at this point (in Node 10, the handshake completes,
secureConnection
fires, and then the client closes the connection without sending any data - that works fine).The below test demonstrates the issue. I haven't committed it, because it only works with Node 12, but hopefully it shows what I'm talking about.
This appears to happen because httpolyglot allows half-open TLS connections, whilst
https.Server
does not. As far as I can tell half-open connections are only allowed by default onhttp.Server
, so I've changed the code here to disable it on sockets once we know that they are definitely TLS.With this change, the above test passes.