Implement stricter checks for fields using RFC 2231 / RFC 5987#470
Merged
Conversation
Values where invalid characters appear in the extended value will now be ignored.
Contributor
Author
|
Once merged, I'll back-port the same fix to 1.x |
Member
garydgregory
left a comment
garydgregory
left a comment
There was a problem hiding this comment.
Hi @markt-asf
Shouldn't the due-to in changes.xml credit the OP?
Contributor
Author
I normally only credit folks that provide (useful) patches rather than just reporting this issue. |
Member
Great. I can cut RCs anytime after that. |
Prompted by CoPilot review
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.
Values where invalid characters appear in the extended value will now be ignored.