feat: added TLS 1.2 support - #248
Merged
Merged
Conversation
ararog
force-pushed
the
add_tls12_support
branch
from
August 21, 2026 23:49
1fb95c8 to
83892d2
Compare
Collaborator
Author
|
@dahankzter just rebased main with your work on deboa-glommio, will fix existing issues tomorrow, push to github and rebase this PR into main. |
This was
linked to
issues
Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Overview
The goal behind this PR is not only add TLS 1.2 support to deboa, but also add some other changes needed on codebase, like better ALPN handling.
TLS 1.2 support
Deboa originally had support to TLS 1.3, but that's not optimal, since several sites still uses TLS 1.2. So now both versions are enabled on rustls.
ALPN handling
Until that moment, ALPN was still not properly implemented, now deboa has partial support, what do I mean with partial support? That means ALPN at client - server level will be restricted to HTTP/1.1 and HTTP/2, which are TCP based protocols, in order to support HTTP/3, it must be done over DNS with an HTTPS record.