-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Ignore unsupported object ACL header? #5706
Comments
We will have to discuss this since ignoring it would mean that we are falsely representing the API and behavior. IMO we should avoid doing such things as it might provide a false representation of API for applications and even cause them to expect a certain type of behavior which will be fake. Please do let us know what is the library you are using we can recommend changes, ACL is considered legacy style and is a legacy way to apply policy on a bucket which lacks flexibility. |
I know, I’ve investigated patching it but unfortunately I haven’t been able to. It’s a closed-source proprietary app called OpenText Media Management. They only just added S3 support a few months ago, and yes, they’re using this deprecated API. That pretty much tells you all you need to know about their software (and no, I can’t stop using it). Maybe a global configuration setting like “ignore unsupported APIs” or “ignore unsupported headers”? That would be disabled by default, to preserve the current behavior, but cases like mine could set this in order to override Minio’s validation. |
Will let you know we can perhaps provide an unsafe mode @GeoffreyBooth |
This needs to be discussed @deekoder - moving this to blocked for discussion. |
@harshavardhana will be sending PR for this soon. |
@GeoffreyBooth we will be supporting |
GetBucketACL call simply returns empty for all GET in ACL requests, the primary purpose of this PR is simply to provide legacy API support for legacy applications. Fixes minio#5706
GetBucketACL call simply returns empty for all GET in ACL requests, the primary purpose of this PR is simply to provide legacy API support for legacy applications. Fixes minio#5706
GetBucketACL call simply returns empty for all GET in ACL requests, the primary purpose of this PR is simply to provide legacy API support for legacy applications. Fixes minio#5706
@GeoffreyBooth we have a PR here would you be able to validate it with your application? #5906 ? |
GetBucketACL call simply returns empty for all GET in ACL requests, the primary purpose of this PR is simply to provide legacy API support for legacy applications. Fixes minio#5706
GetBucketACL call simply returns empty for all GET in ACL requests, the primary purpose of this PR is simply to provide legacy API support for legacy applications. Fixes minio#5706
GetBucketACL call returns empty for all GET in ACL requests, the primary purpose of this PR is to provide legacy API support for legacy applications. Fixes #5706
Not quickly, sorry. |
@GeoffreyBooth you can try now |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I’m trying to use Minio to emulate S3 for an application I’m developing. My app uses a library to upload files/put objects into S3, and I don’t have much control over it. Unfortunately it applies an object-level ACL to every file uploaded, which I know Minio doesn’t support (#4496).
My issue is that Minio returns a 501 error,
A header you provided implies functionality that is not implemented
, on such attempted uploads. Would it be possible for Minio to just ignore this unsupported header? Possibly via configuration?The text was updated successfully, but these errors were encountered: