Skip to content

Modifying the content-type header breaks some integrations #71

Description

@viniciuspinto

The line [1] adds the charset to the Content-Type header and this breaks the integration with some services. In my tests, calling a Bedrock model was returning "The provided Content Type is invalid or nor supported for this model". After removing the line, the issue was gone.

[1] https://github.com/tedder/requests-aws4auth/blob/9e9e7bf25ad1962cd8dd77064216ee4cab8ca520/requests_aws4auth/aws4auth.py#L563C57-L563C72

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions