# Minio: A header you provided implies S3 functionality that is not implemented

**URL:** <https://meta.discourse.org/t/minio-a-header-you-provided-implies-s3-functionality-that-is-not-implemented/134357>\
**Category:** Product Support\
**Created:** [25 בנובמבר,‏ 2019,‏ 10:09am UTC](https://meta.discourse.org/t/minio-a-header-you-provided-implies-s3-functionality-that-is-not-implemented/134357 "2019-11-25T10:09:09Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [25 בנובמבר,‏ 2019,‏ 4:26pm UTC](https://meta.discourse.org/t/minio-a-header-you-provided-implies-s3-functionality-that-is-not-implemented/134357/15 "2019-11-25T16:26:14Z")

</div>

> [@Falco](#):
>
> should we do all the ACL dance even when the setting is disabled? That will break compatibility with all S3 clones out there.

You’re right, I think it is reasonable to only update ACL when the upload needs to be marked as secure. This should fix it: [FIX: Only trigger upload ACL update when needed · discourse/discourse@5c5d8a3 · GitHub](https://github.com/discourse/discourse/commit/5c5d8a307a816afcda4b97eecf49b836fc9ecb01)

Note though @hosna the fix only applies to uploads when creating a new post. There are other operations that trigger an ACL update on the upload (for example, converting topics) and those will probably be still broken using Minio.

---

_[View the full topic](https://meta.discourse.org/t/minio-a-header-you-provided-implies-s3-functionality-that-is-not-implemented/134357)._