If you happen to have a domain on your CF account heres what you'd need to do to possibly make something work:
1: Create a worker that can serve your R2 bucket (add a custom domain my-cdn.mydomain.com) 2: Go to SSL/TLS -> Custom Hostnames and set fallback origin to my-cdn.mydomain.com 3: Click "Add Custom Hostname" enter cubity.getsharex.com 4: Set the cname of cubity.getsharex.com to my-cdn.mydomain.com
Bundling CORS settings into R2 is probably something Cloudflare should consider adding to the roadmap. 90% of people can probably hack it with the Transform Rules to add generous permissions, but there are going to be a lot of gotchas. Using Transform Rules feels very smelly. Amazon has , Backblaze B2 has CORS settings in the bucket management interface, Digital Ocean Spaces also has CORS settings in the management interface. So these services can respond in a fully spec-compliant way.