Skip to content

How to disable Content-MD5 header with S3 PutObject request #2933

Closed
Closed
How to disable Content-MD5 header with S3 PutObject request#2933
Labels
feature-requestA feature should be added or improved.p3This is a minor priority issue

Description

@jmklix
jmklix
opened on Apr 19, 2024

Discussed in #2926

Originally posted by vbrajyaguru April 15, 2024
Hello,

I'm looking for a way to disable content verification on uploads. I'm using PutObjectRequest and set ChecksumAlgorithm::NOT_SET but the request still generated content-md5 header.

Aws SDK 1.11.293
SLES 15 SP4

Activity

  1. jmklix
    added
    feature-requestA feature should be added or improved.
    p3This is a minor priority issue
    on Apr 19, 2024

  2. jmklix commented on Apr 19, 2024

    @jmklix
    jmklix
    on Apr 19, 2024
    MemberAuthor

    @vbrajyaguru
    vbrajyaguru
    Apr 18, 2024
    Author

    Yes, please consider this as feature request. We are using S3 client and using PutObjectRequest to create the PUT request. Our application has its own checksumming method to verify data integrity of the object read from the S3. We don't need data integrity protection while uploading the object to S3 and so we need some way to tell S3 client to not perform checksumming on the content.

    Let me know and I can provide code samples if needed.

  3. rohansuri commented on Oct 1, 2024

    @rohansuri
    rohansuri
    on Oct 1, 2024

    @jmklix any updates on this?

  4. jmklix commented on Oct 2, 2024

    @jmklix
    jmklix
    on Oct 2, 2024
    MemberAuthor

    Sorry, but no updates as of now. It's still in our backlog

  5. sbiscigl commented on Feb 12, 2025

    @sbiscigl
    sbiscigl
    on Feb 12, 2025
    Contributor

    hey sorry for the delay, you can read about the changes in checksumming behavior in #3253

    we also updated some documentation on how this can be achieved, please reference "An API that has checksum when supported and you wish to send no checksum at all with the request" section on how to disable object integrity checks all together, however it is not recommended.

    resolving, let us know if you have any more questions.

  6. sbiscigl
    closed this as completedon Feb 12, 2025

  7. github-actions commented on Feb 12, 2025

    @github-actions
    github-actionsBot
    on Feb 12, 2025 – with 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestA feature should be added or improved.p3This is a minor priority issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions