-
Notifications
You must be signed in to change notification settings - Fork 324
add mc share upload --content-type #1495
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
Conversation
mc share upload --recursive play/mybucket/myprefix/ | ||
.. mc-cmd:: --content-type, T |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if you can specify more than one accepted content type with multiple --content-type arguments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
per eng, you can only specify one
If configured, clients using the generated URL must include a ``Content-Type`` header for the specified type. | ||
MinIO rejects requests that do not have the correct ``Content-Type`` header. | ||
|
||
Content types are also known as `media types <https://www.iana.org/assignments/media-types/media-types.xhtml>`__. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I am being pedantic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. approved
Document
mc share upload --content-type
. Thank you @0xMALVEE 🎉Staged:
https://staging.docs.min.dev/community/minio-object-store/aistor-214-mc-share/reference/minio-mc/mc-share-upload.html
Questions for reviewers:
See https://github.com/miniohq/aistor-object-store-docs/issues/214 for parent issue