New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FormData request header doesn't include boundary #4631
Comments
Can confirm. This breaks file uploads for my React application (web, all references up-to-date). Downgrading to |
0.26.0 doesn't work for me, as payload is broken there. 😬 |
me too, 0.26.1 work for me, but 0.27.1 not work. i am try it with chrome[100.0.4896.127] and safari[15.1 (15612.2.9.1.30, 15612)], it doesn't include boundary |
Looking into it, sorry about that |
I just wasted an hour and a half. |
The below change was introduced in v0.27.0:
Now axios forcibly sets https://stackoverflow.com/questions/39280438/fetch-missing-boundary-in-multipart-form-data-post |
@jasonsaayman hotfix: #4640, #4639, (#4641 or #4596) |
For my college project I needed to upload a file. I found some article that explains how to do that in Vue and I had literally struggled for 5 hours straight with this piece of crap bug to just find out that the authors app used an old version of axios which didn't include this pathetic bug which should never had been introduced, ever... I think I'm done with axios for a few years. At the time of writing this is axios 0.27.1 (latest) |
Thanks to everyone and especially @DigitalBrainJS who helped with this, i will relase 0.27.2 asap. |
Hello. Why is the problem reproduced on axios version 1.1.3 (npm install axios@latest), but works on version 0.27.2 (now it's a minor version?). |
Indeed. I am having bounday-header issues with 1.1.3, but not with ^0.27. Don't get why 😃 |
Describe the bug
Boundary is included in payload, but it's missing in
Content-Type
header - it's justmultipart/form-data
.To Reproduce
Expected behavior
Content-Type
header should have a boundary.Environment
Additional context/Screenshots
n/a
The text was updated successfully, but these errors were encountered: