multipart/form-data without a boundary

Question

Is a multipart/form-data request valid without a boundary? According to the specification when there are more than 1 parts then boundary is used to separate them(and this boundary should not be part of the body). I have a request where there is a single body as a raw content or a file and in the content-type we pass "multipart/form-data" . Is this kind of request actually valid?

Community · Accepted Answer · 2021-10-07 08:14:10Z

10

I think multipart/form-data request without a boundary is invalid.

According to RFC7231, request with only 1 part is still valid multipart MIME type and should follow multipart MIME rules:

MIME provides for a number of "multipart" types -- encapsulations of one or more representations within a single message body. All multipart types share a common syntax ... and include a boundary parameter as part of the media type value.

According to RFC2046, "boundary" is required and mandatory:

The Content-Type field for multipart entities requires one parameter, "boundary".

...

The only mandatory global parameter for the "multipart" media type is the boundary parameter

edited Oct 7, 2021 at 8:14

CommunityBot

11 silver badge

answered May 12, 2017 at 10:24

shaochuancs

16.4k3 gold badges63 silver badges68 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

DaSourcerer Over a year ago

FYI: This is also conclusive with the multipart/form-data media type registry.

Collectives™ on Stack Overflow

multipart/form-data without a boundary

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related