From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH] test/openssl/test_ssl.rb (test_copy_stream): new test
Date: Wed, 25 Nov 2015 21:52:19 +0000 [thread overview]
Message-ID: <20151125215219.3102-1-e@80x24.org> (raw)
I was worried r52750 would break IO.copy_stream with things like
OpenSSL sockets which wrap IOs, but require data to be run through
through encryption/decryption filters. Apparently my worry
was unfounded, but perhaps this test will ensure this case continues
to work.
---
test/openssl/test_ssl.rb | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/test/openssl/test_ssl.rb b/test/openssl/test_ssl.rb
index 9e98a21..06e8d96 100644
--- a/test/openssl/test_ssl.rb
+++ b/test/openssl/test_ssl.rb
@@ -178,6 +178,20 @@ def test_read_and_write
}
end
+ def test_copy_stream
+ start_server(OpenSSL::SSL::VERIFY_NONE, true) do |server, port|
+ server_connect(port) do |ssl|
+ IO.pipe do |r, w|
+ str = "hello world\n"
+ w.write(str)
+ IO.copy_stream(r, ssl, str.bytesize)
+ IO.copy_stream(ssl, w, str.bytesize)
+ assert_equal str, r.read(str.bytesize)
+ end
+ end
+ end
+ end
+
def test_client_auth_failure
vflag = OpenSSL::SSL::VERIFY_PEER|OpenSSL::SSL::VERIFY_FAIL_IF_NO_PEER_CERT
start_server(vflag, true, :ignore_listener_error => true){|server, port|
--
EW
reply other threads:[~2015-11-25 21:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151125215219.3102-1-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).