Someone might paste an entire message with its body to the inputHeaders textarea when using standalone Message Header Analyzer. This causes incorrect processing of the body as headers with the rules for the headers, producing nonsensical rows in the table. Furthermore, on large messages the entire browser can freeze or crash.
Examples
For example, the Multipart Media Type (RFC 2046, 5.1) boundary delimiter from the Content-Type header (14) appears as part of the last header (X-SES-Outgoing, 17) and the rest are not headers.
In another example, HTML message body is interpreted as headers.
Solution
This pull request adds a feature for recognizing the boundary between the header section & the body as defined in RFC 5322, 2.1.
A message consists of header fields (collectively called "the header section of the message") followed, optionally, by a body. The header section is a sequence of lines of characters with special syntax as defined in this specification. The body is simply a sequence of characters that follows the header section and is separated from the header section by an empty line (i.e., a line with nothing preceding the CRLF).
Issue
Someone might paste an entire message with its body to the
inputHeaders
textarea when using standalone Message Header Analyzer. This causes incorrect processing of the body as headers with the rules for the headers, producing nonsensical rows in the table. Furthermore, on large messages the entire browser can freeze or crash.Examples
For example, the Multipart Media Type (RFC 2046, 5.1) boundary delimiter from the
Content-Type
header (14) appears as part of the last header (X-SES-Outgoing
, 17) and the rest are not headers.In another example, HTML message body is interpreted as headers.
Solution
This pull request adds a feature for recognizing the boundary between the header section & the body as defined in RFC 5322, 2.1.