diff options
| author | Sam Roberts <vieuxtech@gmail.com> | 2020-03-20 07:07:36 +0300 |
|---|---|---|
| committer | Beth Griggs <Bethany.Griggs@uk.ibm.com> | 2020-03-24 16:22:50 +0300 |
| commit | 89692ff19b9a4ce03a7f4d4e6949fd2a0a2d6fd2 (patch) | |
| tree | 24cb280adc58d9b50ad51e05f930bfa2c274462c | |
| parent | 76033c5495e48b9fed21780fc86eb089cec2903c (diff) | |
test: end tls connection with some data
In openssl-1.1.1e the client doesn't seem to like having the TLS
connection shut down with no data sent, so send an empty string. A
number of related issues showed up in the TLS1.3 port, so this is
not entirely surprising.
PR-URL: https://github.com/nodejs/node/pull/32328
Backport-PR-URL: https://github.com/nodejs/node/pull/32443
Fixes: https://github.com/nodejs/node/issues/32210
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
| -rw-r--r-- | test/parallel/test-tls-session-cache.js | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/parallel/test-tls-session-cache.js b/test/parallel/test-tls-session-cache.js index 55dd92e81d2..e78c64cbd1f 100644 --- a/test/parallel/test-tls-session-cache.js +++ b/test/parallel/test-tls-session-cache.js @@ -64,7 +64,7 @@ function doTest(testOptions, callback) { throw er; }); ++requestCount; - cleartext.end(); + cleartext.end(''); }); server.on('newSession', function(id, data, cb) { ++newSessionCount; |