Highlight TLS handlers support "custom" protocols#2335
Merged
Conversation
jbellerb
force-pushed
the
jae/push-xrstmtrsywzr
branch
from
43bdf1d to
dd4fc32
Compare
Raw TLS is used by the HTTP handler, but users mostly won't be configuring this. Replaces HTTP examples with examples for MQTT-over-TLS to demonstrate that almost any protocol over TLS works, even if not advertised as supported.
jbellerb
force-pushed
the
jae/push-xrstmtrsywzr
branch
from
dd4fc32 to
1328592
Compare
kcmartin
approved these changes
Jan 20, 2026
Contributor
kcmartin
left a comment
kcmartin
left a comment
There was a problem hiding this comment.
Approved with a minor suggestion
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
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
2 participants
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.
Summary of changes