Incorrectly warns `Skipping data after the last boundary`

[BiDuang]

Latest version (0.0.18) causes the multipart to incorrectly warn Skipping data after last boundary in every multipart request, even when the client sends the correct request format.

Downgrade library can slove this issue.

[Kludex]

Can you show me the request?

Downgrade library can slove this issue.

I issued a security advisory, so I don't recommend that.

[Kludex]

Maybe it's because of two \r\n characters that are at the end?

[BiDuang]

Can you show me the request?

Downgrade library can slove this issue.

I issued a security advisory, so I don't recommend that.

Well, now every multipart request triggers this warning, for example:

curl --location --request POST 'http://localhost:8123/shop/add' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Authorization: Bearer undefined' \
--header 'Accept: */*' \
--header 'Host: localhost:8123' \
--header 'Connection: keep-alive' \
--header 'Content-Type: multipart/form-data; boundary=--------------------------939992003815200322287943' \
--form 'body="{  \"name\": \"foo\",  \"price\": 100.5,  \"description\": \"bar\"}"' \
--form 'img=@"someimg.png"'

[BiDuang]

Maybe it's because of two \r\n characters that are at the end?

Oh, I think that might be the issue. I set a breakpoint and removed the \r\n from the boundary at runtime varible, and the warning is gone now.

[Kludex]

Let me try to fix it real quick.

But again, it's just an annoyance that it sends the warnings - which I intend to fix.

[Kludex]

@BiDuang can you check #193, please?

[BiDuang]

@BiDuang can you check #193, please?

Ok, it works. Thank you.

[Kludex]

Thanks. Released.