This bug is actual mainly for using Ajax.Request along with FormData().
setRequestHeaders() method always sets 'Content-Type' header, even if contentType and encoding options are not defined. It causes incorrect header for Chrome (with comma before the string) that forces to define contentType and enconding. In this case boundary, which is required for multipart/form-data, is missing.
This bug is actual mainly for using Ajax.Request along with FormData(). setRequestHeaders() method always sets 'Content-Type' header, even if contentType and encoding options are not defined. It causes incorrect header for Chrome (with comma before the string) that forces to define contentType and enconding. In this case boundary, which is required for multipart/form-data, is missing.
Probable solution:
Replace
to
It will resolve this problem