Yes it will be fine: https://blog.cloudflare.com/updated-tos/
The Cloudflare Blog
We’re excited to announce new updates that will modernize our terms of service and hopefully cut down on customer confusion and frustration.
EHow many months ago were you remembering?
ZThanks!
ZIt was at the beginning of the open beta, it should be a year and a few months in fact 
EQuite a while! Yes, there was some issues for a while with incorrect ToS flags for R2 usage. Those are now resolved.
Safter I ran the command
rclone purge, I am not able to make the bucket public
AHey everyone, I was wondering what is the advantage of accessing a public R2 bucket via a worker with the Cache API. From my understanding, public r2 buckets are behind the cloudflare cdn with caching right? Does using the cache api provide something more beneficial?
CDepends what you're doing. Workers allow you more flexiblity overall, if you wanted to deny specific paths, require auth, or have a directory listing, and then if you were using a worker for that, you'd have to use the Cache API if you wanted cache at all. If your goal is just to serve what's in your bucket, you can add a Cache rule on the bucket hostname to force caching and set a custom edge cache ttl or upload items with a cache-control header. You'd be avoiding the worker invocation costs as well, as it would still run even for cached items
CI'm assuming you mean accessing the bucket via an r2 binding, and not literally fetching it via a worker
Cthat doesn't sound related to the command, why can't you make it public? Do you get an error? Do you mean adding a custom domain, or enabling the r2.dev subdomain?
AYup, I was referring to the example on the docs - https://developers.cloudflare.com/r2/examples/cache-api/
My usecase is quite simple, I have a few public buckets which host static assets for websites, e.g images, pdfs, audio etc.
I was looking into how to get the most performance out of R2 and any custom settings I need to enable to make this happen. Hence the curiosity about the cache API
My usecase is quite simple, I have a few public buckets which host static assets for websites, e.g images, pdfs, audio etc.
I was looking into how to get the most performance out of R2 and any custom settings I need to enable to make this happen. Hence the curiosity about the cache API
ASo, if I understood you correctly, given I'm just serving static assets publicly, proxying requests to R2 via workers + cache api (as in the example) won't get me anything extra over simply relying on cloudflare's cdn cache?
CIf all the assets are public, just R2 Custom Domain & A Cache Rule to force caching (or upload the objects with a Cache-Control header). You won't be charged for cached hits, and you wouldn't be paying for worker invocations
Cthe cache api would just be accessing the normal cdn cache as well
technically the cache api is just local colo (cloudflare location) cache, where the normal cloudflare cdn cache could be tiered cache or cache reserve, but R2 Custom Domains are special and don't support either
technically the cache api is just local colo (cloudflare location) cache, where the normal cloudflare cdn cache could be tiered cache or cache reserve, but R2 Custom Domains are special and don't support either
Agotcha, thanks for clarifying 
Awould it use tiered cache if I connected a custom domain to the r2 bucket?
Cno
CCache API in Workers doesn't support it at all, and R2 Custom Domains specifically don't either
Si'm added custom domain, but not work
i'm actived r2.dev, after worker..
i'm actived r2.dev, after worker..
Svery strange.. but ok
CYour custom domain doesn't work? What error do you get?
Sbucket dont public
Sit worked after enabling R2.dev subdomain
Sbut it's weird having to do that
Kr2.dev isn't needed for custom domains, they're separate. What error do you see when you try to add the custom domain? Can you take a screenshot?
CHi, could someone help me with r2 (I'm using the aws sdk in go)
Something strange happens because when I run it on my localhost it works fine, the problem arises when I try to run it on a docker image
Something strange happens because when I run it on my localhost it works fine, the problem arises when I try to run it on a docker image
C
Cis is in production? can check your hostname domain in production. Last time my domain was
1.2.0.chientrm.com and it failed. Then I change to 1_2_0.chientrm.com and it works.
Ar2.cloudflarestorage.com/noti is this
Cnoti.97b809ded26d1.r2.cloudflarestorage.comCthis's not gonna work.
AI dmed you
Athe full URL
ZHello, I have one more question, the "CDN" cited in the article is included the use of cache for files that are not cached by default? or is it just for the reverse proxy
KIf you use R2 you can cache any file type
CHi everyone, someone knows if there are plans to have some "intelligent tiering" like in S3 for R2?
OHello.
https://r2-books.oster.dev/ta-today/004.png
by public link i can get metadata in response header?
https://r2-books.oster.dev/ta-today/004.png
by public link i can get metadata in response header?
O
AHello!
When I moved to r2, I uploaded all my files through rclone, and now I upload new ones through the s3 api.
For some reason, the first downloaded pictures open in my browser, and the second ones are downloaded and I am getting the message "Your connection to this site is not secure". They have some kind of different type of access or something like that? I don’t understand how they differ in one bucket if only the download method was different.
When I moved to r2, I uploaded all my files through rclone, and now I upload new ones through the s3 api.
For some reason, the first downloaded pictures open in my browser, and the second ones are downloaded and I am getting the message "Your connection to this site is not secure". They have some kind of different type of access or something like that? I don’t understand how they differ in one bucket if only the download method was different.
CUpdate: I solved it by adding the volume
/etc/sslKAre you using a pubic URL for both?
AI use access through a connected custom domain, it is the same for all photos
KAre you able to share any example links?
KThose both work for me, so my guess is you just need to purge your Cloudflare cache
KBut also: You did not upload this file with the correct
https://img.poisondrop.ru/upload/item_sku/img/desktop/125685AEyXoBOTNIUu.jpeg
Content-Type, it's currently returning application/octet-stream which is the defaulthttps://img.poisondrop.ru/upload/item_sku/img/desktop/125685AEyXoBOTNIUu.jpeg
AThanks a lot! I will investigate the issue
CCaused by: java.lang.Throwable: Acquire operation took longer than the configured maximum time. This indicates that a request cannot get a connection from the pool within the specified maximum time. This can be due to high request rate.
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.
its possible that fix?
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.
its possible that fix?
SWe’re looking at storage tiers in general currently, but the “intelligent” bit is probably going to take a while to land.