Awesome! That would just be for static videos, nothing fancy, HTML5 videos. Thanks ✌️

We uploaded an Image file through the api it got uploaded fine with sucess, but the file is not opening in browser any idea what may be reason of file getting curropted ? PBN_BUCKET.put(fileKey, request.body)

It works great! Thanks for your answers

Removing the slashes does not help

having a weird issue where, if a file stored on R2 loads a JS or CSS file from another bucket, I get a MIME type mismatch (detects

content/octet-stream

but in reality it can be a JS or a CSS file), and this doesn't happen if pulling from the same bucket… Scratching my head over this! (⊙.☉)7

If you're in the R2 dashboard, you are presented with a

Manage R2 API Tokens

button. Not all API tokens show up in there, only ones with the

Account: Workers R2 Storage

permission. However, editing an R2 API Token from the R2 dashboard wipes out all permissions for that token except for the R2 Storage permission. I have an app that is used by thousands of Cloudflare zones that uses 16 permissions (one of them being R2 Storage) and I keep running into an issue where a site loses the 15 other permissions they have for that token because they edited the token from the R2 dashboard. The latest was when a user simply wanted to add IP restrictions to his token and he lost all the other token permissions. See: https://xenforo.com/community/threads/digitalpoint-app-for-cloudflare%C2%AE.206176/post-1628890 It's not the first time this has happened (I'd say I've run into 8-10 support issues because of this at this point). Wouldn't it make more sense to either not delete the other API permissions on the token or make tokens that only have the R2 permission able to be edited from there?

That definitely sounds like a bug. Let me try and repro and I’ll get this fixed

Awesome… been a long-standing issue. I ran into it myself when I first started doing R2 development. Easy enough for me to work around (don’t edit tokens from there), but now that it’s becoming a support issue from my users it’s a little more annoying. 😀

Are you able to share URLs to the different files here?

this happened when calling

put

. does this mean the client connected to the worker disconnected, or there was a network problem between the worker and R2? and if it means the client disconnected from the worker - why was the request outcome

ok

and not

canceled

?

I get that error sometimes as well its something internal and not the client connected to the worker disconnected.

At least in my case its always that, I assume that can possibly show up if the client connected to the worker disconnects (but that should show as cancelled also)

interesting, okay guess I will add some retrying

I'd love to see more automatic retrying when calling DOs, R2, etc

or maybe in this case it could have actually been written

Hi guys, I'm implementing a REST API using workers. I am getting CORS errors when testing it from a browser (it works when using Postman since that is not sending OPTIONS). Any idea where I could configure the CORS rules? thank you!

I get this error while fetching a video from localhost 🤔

cess to fetch at 'https://assets.site.com/video.mp4' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

My CORS rule:

[
  {
    "AllowedOrigins": [
      "http://localhost:5173",
      "http://localhost:4173",
    ],
    "AllowedMethods": [
      "GET"
    ]
  }
]

Where did you configure the rules?

in the r2 settings (CORS Policy)

Do you know if workers have something similar? I am not able to find anything.

I'm not sure they do no 😬

oh 😦

If you’re writing your own Worker, you can just write out CORS headers yourself

I am using itty-router and my CORS config is like this:

It fixed the issue locally, but not after I publish the worker

What request are you sending out?

POSTS

well GET also

GET works