Skip to content
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

Support Callback Negotiation Between Matching ALPNs #2418

Closed
ManickaP opened this issue Feb 22, 2022 · 0 comments · Fixed by #2959
Closed

Support Callback Negotiation Between Matching ALPNs #2418

ManickaP opened this issue Feb 22, 2022 · 0 comments · Fixed by #2959
Labels
feature request A request for new functionality good first issue Good for newcomers
Milestone

Comments

@ManickaP
Copy link
Member

Describe the feature you'd like supported

When a new connection is accepted on the server side, we might want to do the final application protocol selection based on ClientHello SNI. Similar behavior is already supported via TLS over TCP for H/1.1 and H/2.

Original issue: dotnet/runtime#49423

Proposed solution

We would specify the complete list of supported ALPN when we start the listener and then we would narrow down the final ALPN when we set the configuration for the particular incoming connection.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request A request for new functionality good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants