- From: Josh Habdas <notifications@github.com>
- Date: Fri, 19 May 2017 02:41:25 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/540/302657995@github.com>
The `application/form-data` is a MIME type I'm not familiar with and have not seen registered with IANA or elsewhere, so I'm not sure what to make of it. Assuming we're discussing `multipart/form-data` for POST requests the following SO discussion may be useful. But until I have a better understanding time to do more research I'm not going to be of much more use here. http://stackoverflow.com/a/23152871/712334 > I know this is 3 years too late, but Matt's (accepted) answer is incomplete and will eventually get you into trouble. The key here is that, if you choose to use `multipart/form-data`, the boundary must not appear in the file data that the server eventually receives. > The problem with multipart/form-data is that the boundary separator must not be present in the file data (see [RFC2388](http://www.ietf.org/rfc/rfc2388.txt); section 5.2 also includes a rather lame excuse for not having a proper aggregate MIME type that avoids this problem). Please let me know if I can help issue browser bugs to help with behavioral normalization when it makes sense to help me level-up my understanding. Cheers. -- 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/540#issuecomment-302657995
Received on Friday, 19 May 2017 09:42:01 UTC