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

fix(s3): enable content md5 header even if user can't check it #7195

Merged
merged 2 commits into from
Nov 23, 2023

Conversation

fbeauchamp
Copy link
Collaborator

@fbeauchamp fbeauchamp commented Nov 21, 2023

Description

enable content md5 header, required by object lock in case user don't have enough authorization to check if object lock is enable or not

from
https://xcp-ng.org/forum/topic/7939/unable-to-connect-to-backblaze-b2/7?_=1700572613725
following : 796e2ab

user report it fixes the issue : https://xcp-ng.org/forum/post/67633

Checklist

  • Commit
    • Title follows commit conventions
    • Reference the relevant issue (Fixes #007, See xoa-support#42, See https://...)
    • If bug fix, add Introduced by
  • Changelog
    • If visible by XOA users, add changelog entry
    • Update "Packages to release" in CHANGELOG.unreleased.md
  • PR
    • If UI changes, add screenshots
    • If not finished or not tested, open as Draft

@fbeauchamp fbeauchamp requested a review from b-Nollet November 22, 2023 08:39
@fbeauchamp fbeauchamp marked this pull request as ready for review November 22, 2023 08:40
@fbeauchamp fbeauchamp requested a review from julien-f November 22, 2023 14:45
@julien-f julien-f merged commit c4535c6 into master Nov 23, 2023
@julien-f julien-f deleted the fix_s3_permission_object_lock branch November 23, 2023 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants