we can handle broken multipart message now, I believe.

"broken" implies the folloing type message:
* It says Content-Type: multipart but has no multipart block within it.
* multipart without close-delimiter

our analyzer loop does
do { alloc a new part + delimiter
} while ( not reach the end and non-zero data part ).

modify _get_next_pos() which returns (maxlen, maxlen) if broken
condition is satisfied. It means the next part has zero data, so
the next "alloc a new part" process is ignored in analyzer loop.

0 files changed, 0 insertions, 0 deletions