I don't use it personally but it's a blocker for <https://github.com/cloudflare/cloudflare-docs/pull
I don't use it personally but it's a blocker for https://github.com/cloudflare/cloudflare-docs/pull/6008
KOn a similar vain, https://github.com/cloudflare/workers-types hasn't ran since the 1st of Sept so the recent R2 changes like
deletestring[]
M@john.spurlock re denoflare
r2-presigned-url-workervirtualgetonlyIfgetrange: reqHeadersputonlyIf: reqHeaders
K
Kthat and my cursory glance at
workerdworkerdunder
Cloudflare Developer Platform (Cloudflare Workers; Cloudflare Pages; Workers KV; Durable Objects; and R2)Would be surprised if there was hard numbers.
KI'd suspect petabytes would get you a call from sales about moving onto an Enterprise plan
Adaily 7tb 
JJust sat down at the desk this morning - I'll take a look at this today, and respond over on the GH issue. Sounds like I'm going to have to do a denoflare release anyway due to Deno introducing their own global implementation in 1.26+ (finally!)
JHmm, I'm seeing no header returned in S3 api calls. It used to be returned, did something change? I didn't see anything about it in the r2 changelog
(update: is still returned properly in S3 api calls, but not calls)
(update: is still returned properly in S3 api calls, but not calls)
BIs there any transfer-encoding set? What's the last time you saw this working?
Jyep,
transfer-encoding
LHey there! Does somebody know/already succeeded to configure RedisCloud backup to use Cloudflare R2? Their supported list of providers includes Amazon S3 but not Cloudflare R2. Unfortunately, their support does not provide guidance, and S3 configuration works with ACL and not by providing access key/secret key: https://docs.redis.com/latest/rc/databases/back-up-data/
LA solution could be to use FTP protocol but I guess R2 does not support this.
BDoesn't sound like it would work as they need to do the work to create an account from their end. Additionally, we don't support cross-account writes. The easiest path would be for redis to add support for S3 tokens which would work with a similar blast radius as the ACL route once we implement bucket-scoping for tokens
LThanks for your answer. Unfortunately, I feel like it will take months or years before seeing R2 as a working provider. That's sad 
BIf you go through a Worker, you're naturally limited to 100 MiB & you can add a custom limit beyond that
B(200 MiB on Business, 500 MiB by default on ENT but can be customized to not have a limit)
KSorry for tagging you, is that total cache or per file cache?
KNice, thank you
BWe're in the process of adding multipart bindings. For now you could use something like
aws4fetchThanks. I've replied on ticket.