You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[DirectTLS] run user-callbacks on the threadpool, not on the transport event-pump threads #68647
The certificate selector runs synchronously on the pump thread, as do the ClientHello and client-certificate validation callbacks. One blocking callback stalls accept, handshakes, and readiness processing for every connection assigned to this pump. Can we suspend this handshake and run user code away from the event loop?
Area:area-networking (concerns Kestrel's DirectTLS transport, event-pump threads, and the TLS handshake/certificate callback path) Type:Feature (proposes running user callbacks off the event-pump thread onto the threadpool, rather than fixing an existing broken behavior)
DirectTls transport — public API #67909 - DirectTls transport — public API (similarity: medium — same DirectTLS transport work item, related public API surface)
Activity
github-actions commentedon Aug 19, 2026
Triage Summary
Area:
area-networking(concerns Kestrel's DirectTLS transport, event-pump threads, and the TLS handshake/certificate callback path)Type:
Feature(proposes running user callbacks off the event-pump thread onto the threadpool, rather than fixing an existing broken behavior)Potential Duplicates
Notes
https://github.com/dotnet/aspnetcore/pull/67912#discussion_r3755305721).