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
Content type changed from multipart/form-data to application/x-www-form-urlencoded #5067
Comments
I believe that I had to adjust to some changes made in headers processing as well. Adding here in case it helps someone. I am sending an Axios POST request with the following data: And had Headers: In version 0.22.0, the decoded content was: In version 1.0.0+ it is now: The update now seems to be the correct processing if Content-Type is set to 'application/json' (which now seems to work in 1.0.0+) but it initially caused a crash after updating when I tried to load the JSON. |
@Flamenco Don't add |
Can you reproduce the issue here? |
@physicsSorcererKing I am adding it because my base axios, that had all sorts of headers and logic, declared content type of "application/json", as shown. I need to override it. Perhaps overriding it as 'undefined' might work. |
@DigitalBrainJS I found I spelled lowercase |
OK. I found the problem, so I will fix it soon. |
Hi 👋 Please try the latest pre-release by running the following: npm i axios@1.2.0-alpha.1 Please provide feedback in either the pinned issue or discussion thread 🧵 |
@jasonsaayman |
I also had an issue where my headers were getting ignored during a multipart formdata call and Axios was submitting it as a urlencoded form data, which my backend did not likey.
|
Same issue, |
My content-type header of
multipart/form-data
is getting replaced with another content-type. This was not an issue until I switched to v1.0.xHowever, this works:
This was sent with the old version, and the workaround mentioned:
And this started happening when I upgraded.
The text was updated successfully, but these errors were encountered: