mscdex/busboy

Using an = in the boundary returns a malformed content-type error

LeviHarman opened this issue · 1 comments

Hello.
= should be considered a valid character to use for the boundary in a multipart/form-data request.

example content-type that can produce the problem multipart/form-data; boundary====1656457491496===

Seems like it's returning an error in parseContentType

Unquoted parameter values must consist only of token characters, which does not include '='.