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
aws-sigv4 failing to calculate the right signature when using "content-type: multipart/form-data" #13351
Comments
So why do you? When sending a multipart formpost, the update: curl actually can survive the situation and still do a formpost with a boundary so it does not exactly explain the error. Even though the original question why you would use this command line remains. |
So the same error occurs whether or not I give it the |
This confuses me. Your report says
Isn't that quite the opposite of what you just said here? |
I think I might need to clarify then. :) Sorry for the confusion. :) |
Aha, ok. Thanks for clarifying. |
I suspect this is because the generated |
For context what we have done previously that worked was:
This has worked fine until we needed to upload multiple files. |
I did this
NOTE: Changing the actual paths and hashes to some redacted values.
Which gave me the following output:
When using the curl command with only a single file and without
Content-Type: multipart/form-data
everything works as expected, but fails to sign properly when givenContent-Type: multipart/form-data
.I expected the following
I expect for the signing to work and hit the logic behind my endpoint.
curl/libcurl version
operating system
The text was updated successfully, but these errors were encountered: