- Cloudflare Developers

Cloudflare Developers•4y ago

kian

Erisa•9/21/22, 9:29 PM

You absolutely can change their headers with transform rules

kianOP•9/21/22, 9:31 PM

Should work straight away

kianOP•9/21/22, 9:33 PM

Kkian Click to see attachment

Charuwts•9/21/22, 9:37 PM

Would this make it possible for presigned direct uploads from a frontend?

kianOP•9/21/22, 9:37 PM

This is for public buckets, so no

kianOP•9/21/22, 9:37 PM

You can't add CORS headers to the SigV4 endpoint yet

Charuwts•9/21/22, 9:38 PM

Bummer

SnowRunescape•9/21/22, 10:17 PM

problem of r2 bucket

SnowRunescape•9/21/22, 10:17 PM

Cyb3r-Jak3•9/21/22, 10:18 PM

That is the firewall checking your connection to the bucket

SnowRunescape•9/21/22, 10:19 PM

this is bad, the images do not load...

Unsmart•9/21/22, 10:20 PM

You will need to tone down your security rules

SnowRunescape•9/21/22, 10:20 PM

Unsmart•9/21/22, 10:21 PM

It's not a problem with R2, you are just getting stopped by your firewall settings.

SnowRunescape•9/21/22, 10:23 PM

I wish I had activated the protection and not have to go through this in the images

SnowRunescape•9/21/22, 10:23 PM

I understand that I will have to create a rule for this, but you's could adjust...

Unsmart•9/21/22, 10:24 PM

We cant adjust your settings if you make them start blocking real people

Kkian Click to see attachment

Karew•9/22/22, 12:34 AM

This is technically not valid CORS, but I suppose most things won’t care? Have you tried it in the wild?

Unsmart•9/22/22, 12:34 AM

How is that not valid cors?

Karew•9/22/22, 12:35 AM

You’re not supposed to blindly answer every HTTP request with CORS headers

kianOP•9/22/22, 12:35 AM

kianOP•9/22/22, 12:35 AM

You can just add this if you only want it on requests

Unsmart•9/22/22, 12:37 AM

the MDN for cors shows it responding with the headers for both ends (i.e. options and post)

SakuraFC•9/22/22, 12:37 AM

You can make allow origin dynamic and add http.request.headers["origin"][0] as header field

SakuraFC•9/22/22, 12:38 AM

This will only have header on requests with origin in it

Karew•9/22/22, 12:46 AM

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.

Unsmart•9/22/22, 12:48 AM

Seeing as they have already talked about wanting feature parity with S3 that is probably coming soon. soontm

KKarew Bundling CORS settings into R2 is probably something Cloudflare should consider ...

Darkle•9/22/22, 1:08 AM

Yes, I agree with this, CORS settings are pretty essential, Backblaze B2 settings for CORS are great, adding that same to the R2 dashboard would be the ideal solution

Darkle•9/22/22, 1:10 AM

I wonder if now that it is officially GA the pace of updates to R2 will be limited to achieve greater stability(?)

beelzabub•9/22/22, 1:10 AM

Yeah. I just finished off the PR today. It’s a big boi so it’ll take time to review / land / release. But I’m optimistic sooner rather than later

Darkle•9/22/22, 1:12 AM

Are you referring to the CORS settings? or am I missing something, sorry

SSome Call Me Tim Ahh, good timing, was just getting a bunch of CORS errors trying to stream some ...

Unsmart•9/22/22, 1:47 AM

You can use transform rules in the interim : r2

Dyno•9/22/22, 2:18 AM

How useful is streaming sigv4 support

YES I NEED THIS

Neat

Poll by beelzabub#0369

•

9/22/22, 2:18 AM

beelzabub•9/22/22, 2:20 AM

Streaming sigv4 is a way to upload in a cryptographically verified way without computing the file checksum beforehand (it basically sends it like a HTTP chunked transfer and can be combined with HTTP chunked transfer as well) . Support within SDKs is mixed. This doesn't remove the need for the length of the file (that's provided in the header since will be incorrect or even unset if combined with HTTP chunked transfer).

Raiyan•9/22/22, 3:22 AM

What a bummer, I had a bucket connected to that domain before, then I deleted it, and created a new one and it won't accept the domain. The DNS is already edited, but it won't accept, neither it let me delete the record.