Closed pmakholm closed 7 years ago
I have a mail with the following Content-Type header:
Content-Type: multipart/mixed; boundary = "--=_Next_Part_24_Nov_2016_08.09.21"
(note the space after boundary)
boundary
This is parsed as an attribute named boundary (including a space at the end) where my code expects an attribute named boundary.
It is not obvious to me whether RFC 1512 allows a space char between the attribute name af the =, but unfortunately I've seen it happen in the wild.
=
I have a mail with the following Content-Type header:
(note the space after
boundary)This is parsed as an attribute named
boundary(including a space at the end) where my code expects an attribute namedboundary.It is not obvious to me whether RFC 1512 allows a space char between the attribute name af the
=, but unfortunately I've seen it happen in the wild.