I am encountering an issue with Cloudflare R2 storage where the Content-Type response header is not present when I use a presigned URL to perform a GET or HEAD request on an object. This absence of the Content-Type header is impacting my application's ability to handle the response properly. I have already checked the CORS settings for my R2 bucket to ensure that the Content-Type header is allowed and exposed. Despite this, the header still does not appear in the response. Could you please assist me in resolving this issue? Is there a specific configuration or step that I might be missing to ensure that the Content-Type header is included in the response when using presigned URLs?
Hey, We need help to debug some error, where can get support related to R2. Do we have any specific channel for R2 support. we are getting 500 internal error from cloudflare some times using s3 api while writing file object got error Unexpected (temporary) at Writer::close.
To contact Cloudflare Support about an issue, please visit the Support Portal and fill in the form on the portal. After submission, you will receive confirmation over email.
Some issues, such as Account or Billing related issues, cannot be solved by the community. Any plan level can open a ticket for these topics. For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs
Does S3 support it? It's unlikely we'll support something that S3 doesn't in the S3 api but I suppose maybe in the workers api it could be feasible. When I last checked AWS S3 docs they suggested to copy the object to itself, this isn't a paradigm we invented as far as I know