To summarize my findings (and interpretation):
1. Any "multipart/*" type is a "Content-Type". It is not a kind of
"Transfer-Encoding". It is a property of payload.
2. HTTP/1.1 requires sender to specify the end of the payload by
specifying either "Content-Length" or "Transfer-Encoding" (with fin
Hello,
Looks like Chrome and Firefox just unable to process chunked encoding
together with multipart/x-mixed-replace.
Actually "multipart/x-mixed-replace" was never standardized for HTTP.
We have other forms of "multipart/" defined for HTTP:
* "multipart/form-data" for requests, see
https://d
