Re: [whatwg/fetch] [Suggestion] Add more per-file (custom) header to multipart (#1130)

if `content-length` was know for each entry (not just for file's) then it would make it easier for backends to pass x amounts of bytes throught instead of scanning the hole body for a boundary every time.

Imo i think that the boundary was a bad style decision. smarter containers like zip, tar and other multi file container specifies the byte length instead in the beginning or before every entry or at the end in some central dictionary so you can jump/scan a hole blob without having to scan for a boundary separator. 

So i think that a content-length header would be an enhancement to the multipart/form-data specification.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1130#issuecomment-751413681