Amplify API PUT/POST only sends "application/json" content-type

[tylerjroach]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.

Language and Async Model

Not applicable

Amplify Categories

REST API

Gradle script dependencies

All Versions

Environment information

All Versions

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

Customers are free to pass their own Content-Type header into POST/PUT requests. This provided header is part of this sigv4 signature.

However this line results in application/json being the actual Content-Type sent to the server:

amplify-android/aws-api/src/main/java/com/amplifyframework/api/aws/auth/IamRequestDecorator.java

Line 102 in f3f8caf

requestBody = RequestBody.create(bodyBytes, JSON_MEDIA_TYPE);

This will result in response failing due to signature mismatch.

Customers should be able to provide their own Content-Type. The fix should grab content-type from customer headers if one exists, otherwise fallback to application/json then sign. The RequestBody.create method should then pass the proper content type instead of the hardcoded JSON_MEDIA_TYPE.

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

amplifyconfiguration.json

No response

GraphQL Schema

// Put your schema below this line

Additional information and screenshots

No response

[tylerjroach]

This fix for this issue has been released in Amplify 2.14.10 🎉

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.