-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct complete_io
behaviour when close_notify
alert is received
#1905
Conversation
Have a test that demonstrates another route to reaching this state: a fully & cleanly closed connection.
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1905 +/- ##
=======================================
Coverage 95.49% 95.49%
=======================================
Files 86 86
Lines 18646 18650 +4
=======================================
+ Hits 17806 17810 +4
Misses 840 840 ☔ View full report in Codecov by Sentry. |
Maybe worth mentioning the new API fn? "Add an API, |
Release notes:
rustls::ConnectionCommon::complete_io
, reachable via network input. If aclose_notify
alert is received during a handshake,complete_io
did not terminate. Callers which do not callcomplete_io
are not affected.handshake_kind()
) for learning whether a handshake was resumed or not.