Add content type validation as specified in RFC 9052#292
Open
aahajj wants to merge 1 commit intolaurencelundblade:masterfrom
Open
Add content type validation as specified in RFC 9052#292aahajj wants to merge 1 commit intolaurencelundblade:masterfrom
aahajj wants to merge 1 commit intolaurencelundblade:masterfrom
Conversation
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.
Implemented validation for textual content type values to ensure they follow the
<type-name>/<subtype-name>format as required by RFC 9052, Section 3.2.Currently, setting a content type is allowed when signing a message. When encryption and the other functionalities are implemented/merged, setting a content type must be moved somewhere else, right?
I've put the validation in
utiljust so that it can be used in the future when content type can be used across the library.