Skip to content
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

Fetch: multipart/form-data content type header should not be set in fetch client #1531

Closed
jamesleeht opened this issue Jul 22, 2024 · 0 comments · Fixed by #1532
Closed

Fetch: multipart/form-data content type header should not be set in fetch client #1531

jamesleeht opened this issue Jul 22, 2024 · 0 comments · Fixed by #1532
Assignees
Labels
bug Something isn't working fetch Fetch client related issue
Milestone

Comments

@jamesleeht
Copy link
Contributor

jamesleeht commented Jul 22, 2024

multipart/form-data content type header should not be set when using fetch:
https://muffinman.io/blog/uploading-files-using-fetch-multipart-form-data/

If not the boundaries will not be properly set.

Originally posted by @jamesleeht in #1529 (comment)

@melloware melloware added this to the 7.0.1 milestone Jul 22, 2024
@melloware melloware added the bug Something isn't working label Jul 22, 2024
@melloware melloware added the fetch Fetch client related issue label Jul 23, 2024
@melloware melloware changed the title multipart/form-data content type header should not be set in fetch client Fetch: multipart/form-data content type header should not be set in fetch client Jul 23, 2024
@soartec-lab soartec-lab self-assigned this Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fetch Fetch client related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants