Content-Type header in multipart does not contain required parameter boundary

RFC: https://tools.ietf.org/html/rfc7578#appendix-A

Related Comment and issue: https://github.com/django/channels/issues/1386#issuecomment-568215439 https://twistedmatrix.com/trac/ticket/9739

Background:

Consider a multipart request as such:

Body:

--d66f495a-c4d1-487c-9277-9ab1a20001cc
Content-Disposition: form-data; name="content"
Content-Type: multipart/form-data; charset=utf-8

Anything
--d66f495a-c4d1-487c-9277-9ab1a20001cc--

Header: Content-Type: multipart/form-data; boundary=d66f495a-c4d1-487c-9277-9ab1a20001cc

A new change in Python 3.7 considers this request multipart header as invalid, which according to @twm is not compliant with the latest change in the RFC (2015).

Hence, on new Python versions, when the request is parsed, it tries to get the boundary from the multipart body Content-Type header and it returns empty string since there is none, and throws saying that is is Invalid Boundary

[twm]

I don’t see anything in https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/MultipartBody.kt that would generate this header. Nor do I see such sniffing here https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/RequestBody.kt Does your application code set it?

[iamareebjamal]

Thanks. Will try and revert