diff options
| author | Jan Engelhardt <[email protected]> | 2019-10-04 20:51:05 +0000 |
|---|---|---|
| committer | Jan Engelhardt <[email protected]> | 2019-10-05 09:31:51 +0000 |
| commit | df32418df5af976566e6eecb2777ccab7eadf5b3 (patch) | |
| tree | 140cafe67e9d5d332d557f11e7a56c854c54c440 /tests/parser/bodyPartTest.cpp | |
| parent | Reduce indent by 3 levels in findNextBoundary (diff) | |
| download | vmime-df32418df5af976566e6eecb2777ccab7eadf5b3.tar.gz vmime-df32418df5af976566e6eecb2777ccab7eadf5b3.zip | |
Disregard whitespace between leading boundary hyphens and marker
The way I read the RFC is that whitespace is not allowed before the
boundary marker, only afterwards, so the checks for leading WS are
removed, and the missing check for trailing WS is added.
See RFC 2046 ยง5.1.1: """The boundary delimiter line is then defined
as a line consisting entirely of two hyphen characters ("-", decimal
value 45) followed by the boundary parameter value from the
Content-Type header field, optional linear whitespace, and a
terminating CRLF."""
Diffstat (limited to '')
| -rw-r--r-- | tests/parser/bodyPartTest.cpp | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/parser/bodyPartTest.cpp b/tests/parser/bodyPartTest.cpp index 91742553..062007d9 100644 --- a/tests/parser/bodyPartTest.cpp +++ b/tests/parser/bodyPartTest.cpp @@ -213,9 +213,9 @@ VMIME_TEST_SUITE_BEGIN(bodyPartTest) vmime::string str = "Content-Type: multipart/mixed; boundary=\"MY-BOUNDARY\"" "\r\n\r\n" - "-- \t MY-BOUNDARY\r\nHEADER1\r\n\r\nBODY1\r\n" + "--MY-BOUNDARY \t \r\nHEADER1\r\n\r\nBODY1\r\n" "--MY-BOUNDARY\r\n" - "-- MY-BOUNDARY--\r\n"; + "--MY-BOUNDARY-- \r\n"; vmime::bodyPart p; p.parse(str); @@ -291,7 +291,7 @@ VMIME_TEST_SUITE_BEGIN(bodyPartTest) vmime::string str = "Content-Type: multipart/mixed" "\r\n\r\n" - "-- \t UNKNOWN-BOUNDARY\r\nHEADER1\r\n\r\nBODY1\r\n" + "--UNKNOWN-BOUNDARY \t \r\nHEADER1\r\n\r\nBODY1\r\n" "--UNKNOWN-BOUNDARY\r\nHEADER2\r\n\r\nBODY2\r\n" "--UNKNOWN-BOUNDARY--"; |