Uploading files and multipart data

[akre54]

Uploading files and multipart data

[akre54]

It should be possible to override the headers object for those cases where you need to do something special. Let me know if that's not sufficient and we can reopen.

[skinnyjames]

That's sort of the issue.
By overriding the headers to have a content type of "multipart/form-data," the server errors that the multipart boundary can't be found.

This seems to be an issue with how fetch itself works, based on other's experiences. The recommendation is to take the content-type out of the headers and let the browser generate it.

It's interesting because when I set the content-type to undefined I expect the defaults function to override it with 'application/json', but it comes through as a string e.g. - "content-type": "undefined". This might have to do with the way backbone's sync method works, but I still imagine that if the content-type header did come through as undefined, the defaults method would still override it.

Any ideas?

[akre54]

Unfortunately with the defaults function there's no nice way to remove a key, only override it. Maybe try with an empty string, or null?

It looks like fetch (or at least the fetch polyfill) has its own logic for when the content-type header is falsey. (I think this is the section in the spec, so should work in native implementations too).

[skinnyjames]

Thanks for your help!

I tried the above. I don't quite understand why falsey values are being quoted/literalized when I inspect the request object from node - using the fetch polyfill it correctly sets the content-type/boundary, but chrome v55 doesn't. Fetch seems cool, but I think i'll just switch back to jQuery for now.

Thanks again

[akre54]

Sure, sorry to hear it.

Maybe as a last option, pass an headers object instead of trying to set the content-type directly? Should work. Otherwise if you can think of a good solution it might help the next person too.