@john.spurlock re denoflare `r2-presigned-url-worker` ... it seems to be bound to one and only one R

@john.spurlock re denoflare

r2-presigned-url-worker

r2-presigned-url-worker

... it seems to be bound to one and only one R2 bucket, but still redundantly requires the bucket name be included as a URL path prefix... which could be avoided by configuring S3 tooling that generates presigned URLs to use

virtual

virtual

addressing style... but even that would then require that the bucket name be used as the subdomain where the worker is deployed, and not let me use any domain... am I understanding correctly?

kian•10/7/22, 1:54 PM

works fine

kian•10/7/22, 1:54 PM

with doesn't and with doesn't

kian•10/7/22, 1:56 PM

kian•10/7/22, 1:57 PM

kian•10/7/22, 2:00 PM

The original idea from Vitali was that the object it's receiving is malformed (r2) but that sounds like something in the runtime as opposed to anything that the user can control in the Worker, since the header is sound syntactically.

kian•10/7/22, 2:04 PM

that and my cursory glance at indicates it's going down a code path that isn't in so my input is limited haha

kian•10/7/22, 2:05 PM

https://www.cloudflare.com/en-gb/supplemental-terms/

kian•10/7/22, 2:05 PM

under

kian•10/7/22, 2:18 PM

Would be surprised if there was hard numbers.

kian•10/7/22, 2:18 PM

I'd suspect petabytes would get you a call from sales about moving onto an Enterprise plan

albert•10/7/22, 3:05 PM

daily 7tb

Mmrmachine @john.spurlock re denoflare `r2-presigned-url-worker` ... it seems to be bound t...

John Spurlock•10/7/22, 3:42 PM

Just 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!)

John Spurlock•10/7/22, 4:20 PM

Hmm, 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)

JJohn Spurlock Hmm, I'm seeing no `content-length` header returned in S3 api `getObject` calls....

beelzabub•10/7/22, 5:42 PM

Is there any transfer-encoding set? What's the last time you saw this working?

Bbeelzabub Is there any transfer-encoding set? What's the last time you saw this working?

John Spurlock•10/7/22, 5:51 PM

yep, set to chunked. not sure the last time I personally tested this code path, perhaps back around when R2 launched public read support?

Laurent Pellegrino•10/7/22, 5:54 PM

Hey 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/

Laurent Pellegrino•10/7/22, 5:55 PM

A solution could be to use FTP protocol but I guess R2 does not support this.

LLaurent Pellegrino Hey there! Does somebody know/already succeeded to configure RedisCloud backup t...

beelzabub•10/7/22, 6:03 PM

Doesn'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

Laurent Pellegrino•10/7/22, 6:15 PM

Thanks for your answer. Unfortunately, I feel like it will take months or years before seeing R2 as a working provider. That's sad