client: accept application/pkcs7-mime for csrattrs endpoint#47
Open
kalvdans wants to merge 1 commit into
Open
Conversation
…or csrattrs endpoint RFC 7030 Section 4.4 specifies application/pkcs7-mime for the csrattrs response, but the globalsign/est client historically used the non-standard application/csrattrs MIME type. This change makes verifyResponseType accept multiple acceptable content types and updates the CSRAttrs call to accept both MIME types, ensuring interoperability with both RFC-compliant servers and the client's own historic behavior. Added unit tests for: - CSRAttrsRFC7030: accepts application/pkcs7-mime per RFC 7030 - CSRAttrsNonStandard: accepts application/csrattrs (non-standard) - CSRAttrsWrongType: rejects application/pkcs10
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.
RFC 7030 Section 4.4 specifies application/pkcs7-mime for the csrattrs response, but the globalsign/est client historically used the non-standard application/csrattrs MIME type. This change makes verifyResponseType accept multiple acceptable content types and updates the CSRAttrs call to accept both MIME types, ensuring interoperability with both RFC-compliant servers and the client's own historic behavior.
Added unit tests for:
AI disclosure: Minimax-M2.7 was used to make the patch.