EMAIL-212 MIME closing boundary delimiter incorrectly accepted when followed by extra characters#380
Open
spencerwuwu wants to merge 1 commit intoapache:masterfrom
Open
EMAIL-212 MIME closing boundary delimiter incorrectly accepted when followed by extra characters#380spencerwuwu wants to merge 1 commit intoapache:masterfrom
spencerwuwu wants to merge 1 commit intoapache: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.
Submit a failing testcase for the issue reported at Jira EMAIL-212
According to RFC 2046 §5.1.1, a boundary delimiter line is defined as:
Tested on a few peer implementations and found that they all obtained the body content as shown in the unit test.