Because as Kian mentioned the SPA does
Because as Kian mentioned the SPA does not have a server so the cors approach would never really work as the 'client' can't really respond (if i got it correctly)
SSetting up a bucket's CORS policies is a one time thing only. You can do it from your local machine instead of trying to do it from your app
SThat's what Kian was sayng. You cannot set up CORS from a browser because you would need CORS set up in the first place to be able to do that. Chicken-and-egg
MOh, so I can setup cors one time and then the bucket keeps those settings?
MHow should I do that?
MSo its a matter of configuring the bucket then?
SYep! So like I said, the only way to configure CORS is via the S3 API. So you'd have to set up the S3 SDK locally. Then it is a matter of sending out a PutBucketCors command.
A CORS UI is in the works and will arrive soon, but it doesn't exist yet
A CORS UI is in the works and will arrive soon, but it doesn't exist yet
SThis is what that could look like:
MI have set the bucket cors via
and just checked via
I get back
as the defined bucket-cors
and yet still get the
and just checked via
I get back
as the defined bucket-cors
and yet still get the
MAny idea on how to address this?
Mnevermind. Silly mistake on my end. changed into
SOh um, you shouldn't need that
Mit didn't work without it
Mand now everything is working as I would expect it to!!
MThank you a lot for you extremely useful guidance!!!
MPerhaps a useful thing to add to the docs currently (as the UI is not yet working)
- Add this to inside the scripts
- Replace with your R2 bucket name
- Replace with your cloudflare User ID
- Create a file with your desired settings
- To apply the rules do:
- (To set the CORS rules)
- (To check if it applied correctly)
SOh that's interesting, but glad it is working! The UI, along with a docs update specifically for CORS is coming very soon though!
SActually, you know what, you are totally correct about needing BTW