Add support of SNI #1466
Merged
Add support of SNI #1466
Conversation
This file contains 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
Open
sbernard31
force-pushed
the
sni
branch
2 times, most recently
from
d6cf2bc
to
b8c65b7
Compare
sbernard31
force-pushed
the
master
branch
2 times, most recently
from
8e7cd35
to
2efb924
Compare
|
This is now integrated in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add support of SNI at client side.
Add some integrations tests about SNI.
At server and bootstrap server, there is no specific Leshan abstraction for now, we just use Californium API to support SNI for
coapswith rpk and x509.Note there is also no support added to demo. (If you are using a bootstrap server which is able to put SNI resource (id:14) of Security object (id:0) to a leshan-client-demo, it should be able to use it)
More details at #1447.