fix(fetch): remove Content-Type without boundary for FormData#7314
Merged
jasonsaayman merged 2 commits intoaxios:v1.xfrom Apr 8, 2026
Merged
fix(fetch): remove Content-Type without boundary for FormData#7314jasonsaayman merged 2 commits intoaxios:v1.xfrom
jasonsaayman merged 2 commits intoaxios:v1.xfrom
Conversation
When using the fetch adapter with FormData and manually setting Content-Type to 'multipart/form-data' (without boundary), the request would fail because the boundary is required. This fix detects when Content-Type is set to multipart/form-data without a boundary and removes it, allowing fetch to automatically set the correct Content-Type header with the proper boundary. Fixes axios#7054
7ef2c1b to
311e0b4
Compare
jasonsaayman
approved these changes
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Content-Type: multipart/form-datawould result in a missing boundarymultipart/form-datawithout a boundary and removes it, allowing fetch to automatically set the correct header with the proper boundaryTest plan
Fixes #7054