fix: multipart/form-data header issues with node/js fetch targets #230
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since #227 has us a bit spooked we've started testing other targets that may also have issues with
multipart/form-datarequests and found that both of thefetchtargets for Node and JS are not currently transferring data properly because the custom header that is being added is clashing with the auto-generated header from theFormDataAPI andform-datamodule.You can see this problem in action with the
multipart-form-datasnippet against https://httpbin.org/anything:After removing the
multipart/form-dataheader: