Skip to content

[DirectTLS] run user-callbacks on the threadpool, not on the transport event-pump threads #68647

Closed

Description

@DeagleGross

A follow-up suggestion by Stephen:

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?

Activity

  1. added this to the 11.0-rc2 milestone on Aug 19, 2026
  2. self-assigned this
    on Aug 19, 2026
  3. added
    area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
    on Aug 19, 2026
  4. github-actions commented on Aug 19, 2026

    @github-actions
    Contributor

    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

    Generated by Issue Triage Agent for dotnet/aspnetcore for #68647 · auto · 47.7 AIC · ⌖ 3.24 AIC · ⊞ 27.6K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions