We encountered an issue where doing a multipart POST resulted in the server not being able to parse the resulting multipart body.
On further examination we figured out that this happened due to the Content-Type that is set automatically when you switch the body type to Multipart form data is missing the boundary parameter. (multipart/form-data instead of multipart/form-data; boundary=------border)
We encountered an issue where doing a multipart POST resulted in the server not being able to parse the resulting multipart body.
On further examination we figured out that this happened due to the Content-Type that is set automatically when you switch the body type to
Multipart form datais missing theboundaryparameter. (multipart/form-datainstead ofmultipart/form-data; boundary=------border)The RFC seems to indicate that this parameter is required when using this Content-Type: https://tools.ietf.org/html/rfc7578#section-8