Replies: 1 comment 2 replies
|
Please use this method: Instead of …RustFS will store it as custom object metadata. By S3 conventions, custom metadata is prefixed with x-amz-meta-. So the header actually returned to the browser is: |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm migrating from Minio and am trying to configure the Cache-Control header on the response for assets in a public bucket. Attempting to pass the value to rustfs sets the "x-amz-meta-cache-control" header with the correct value, but the browser does not handle this.
Is there a way to configure the response to use the regular Cache-Control header or is it necessary to proxy the request with Nginx or Cloudflare to set it?
All reactions