Add new_server_side_from_acceptor to allow init from a pre-existing Acceptor #33
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.
In certain cases, a TLS server may need to pre-process the incoming bytes (eg: it may want to peek to see if this is raw HTTP, or HTTP over SSL) before deciding to hand it off to a
TlsStream
. BecauseTlsStream
uses rawTcpSocket
, there's no way to re-inject any sniffed bytes that wereread()
rather thanpeek()
'd from the socket.This adds a new
new_server_side_from_acceptor
where an initialAcceptor
can be passed in. It may contain either the full handshake or just a few prefix bytes that were sniffed from the socket earlier.We test this by creating a new TLS pair where the socket sniffs the first 8 bytes of the client handshake before firing up its TlsStream.