hi, i'm wondering how to use cloudflare cdn with r2? shall i put a different domain name or just usi
hi, i'm wondering how to use cloudflare cdn with r2? shall i put a different domain name or just using the r2 domain name is enough ?
DIf I want to connect to my R2 bucket form my PC do I need to make the URL public or if I have the API keys then it's enough?
EThe included
r2.dev subdomain has rate limits in place and won't take advantage of CDN features like WAF and caching - its recommended to attach a custom domain
KSo the R2 Migrator will just migrate the entire bucket in the background over time? I thought it was originally supposed to migrate files on demand as end users, etc try to access them?
CThis is what they promised for the first iteration in https://blog.cloudflare.com/cloudflare-r2-super-slurper/
(The thing you are talking about will come later according to that, or just use Kian's)
(The thing you are talking about will come later according to that, or just use Kian's)
MCorrect. Explicit migration to start; on-the-fly later. An explicit, one time migration can be useful for cases with a lot of long tail content, and/or where you want to cut away from the other provider sooner 
KIssue on the R2 token page:
- You have a token with an expiration date
- Edit the token
- The expiration field is automatically changed to "Forever" (!)
- That change isn't saved (!)
Uyup they know 
Uyou can change the expiry to anything but forever atm
Ethis was discussed in a conversation above somewhere and was reported to be resolved by now, but possibly not.
tldr yes there was changes, the S3 APIs now support regions, WNAM is one of them and there was an issue causing that exact error that Sid looked into
tldr yes there was changes, the S3 APIs now support regions, WNAM is one of them and there was an issue causing that exact error that Sid looked into
getting stone walled by supportIf you pass me the ticket id I can look at it in the morning
Kthis might be an old question, but does r2 supports http2 protocols? currently I'm seeing the files are loaded via http1
KI'm using public buckets, and image are loading via http1
KYeah Iām pretty sure public buckets only do 1.1 like the S3 API
K
KI believe someone said a long time ago that R2 public domains are only HTTP/1.1, there's no real benefit to them being HTTP/2
Kthanks
KPeak daily usage last I recall
KSo whatever the highest amount of usage was for a given day
SYou'll see status page updates when we declare an incident, and we didn't when this bug was reported (primarily because I didn't see a lot of complaints outside of Discord and our internal alerts didn't fire, indicating that this bug wasn't too prevalent).
For major issues you'll definitely see a status page incident
For major issues you'll definitely see a status page incident
DSeems like a strange thing to think. While R2 wouldn't be a great candidate for all HTTP/2 features, I'd think R2 public buckets would use HTTP request concurrency a lot for a site that is storing static assets on them (think like a photo site where a user is looking at a page of thumbnails coming from R2). HTTP/2 Multiplexing > HTTP/1.1 connection reuse. Also, the ability to compress HTTP headers is nice (a little less network traffic needed for every request isn't a bad thing either).
K
KYou can't store anything but a
GETmatch has an ignoreMethod optionEusually yes
SI was thinking of offloading my zoom cloud recordings to R2 with a webhook + CF worker proxy, but I'm a little unsure how the pricing works out for the whole thing.
My recordings total ~1tb/month or 50k-60k minutes/month right now. Most recordings are ~500mb but can occasionally peak to ~4gb.
My recordings total ~1tb/month or 50k-60k minutes/month right now. Most recordings are ~500mb but can occasionally peak to ~4gb.
SThe R2 pricing seems straight forward @ ~$15 for the 1tb but idk what the pricing for the worker that proxies the recording videos would be?
KMy particular R2 public domain is not, do you have an R2 public URL that is?
KThe public domains also don't respond via HTTP/2, at least all of mine don't
Aah ok. @zeblote was reporting it loads over h2 for them with public endpoint. it'd be good to find out what's going on here
A@karew you have http/2 enabled in your CF panel?
KYep
KSome of the website settings don't affect R2 custom domains. They also don't enforce TLS 1.2+ even if you set that requirement.
DYa, the API isn't as big of a deal, but hopefully we'll get something better than HTTP/1.1 on R2 public buckets someday... It's funny looking at the request waterfall for my sites and it's all coming down via HTTP/3... except for images on R2... those are HTTP/1.1. Welcome to the 1999. 
Awell... let's wait to hear what's going on with @zeblote's account, since they claim to be getting HTTP/2 on R2 public bucket. maybe this is just some flag somewhere or something.