Correctly implement encoding / decoding Key Configuration Media Type #75
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
Motivation: We didnt correctly implement encoding / decoding as we missed to prefix the length as defined in https://www.rfc-editor.org/rfc/rfc9458.html#section-3.2 Modifications: - Add new methods and deprecate the old ones - Correctly handle the prefix - Adjust tests Result: Correctly follow https://www.rfc-editor.org/rfc/rfc9458.html#section-3.2
|
@thomdev PTAL |
normanmaurer
force-pushed
the
encoding_decoding
branch
from
453130d to
2fddc28
Compare
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.
Motivation:
We didnt correctly implement encoding / decoding as we missed to prefix the length as defined in https://www.rfc-editor.org/rfc/rfc9458.html#section-3.2
Modifications:
Result:
Correctly follow https://www.rfc-editor.org/rfc/rfc9458.html#section-3.2