But you still may need to clear old cache items if you got them cached. You can purge your whole cac
But you still may need to clear old cache items if you got them cached. You can purge your whole cache or clear individual items.
SAre you referring to the Workers sub-request limit? If so, yeah one fetch counts as one sub request, regardless of what you do in that request.
SThanks!
Swho clean all objects of r2? easy?
Swithout delete bucket
HLike ?
HThough I would probably
--dry-run
SThank you, i did that and it worked. However, i would love to have a cache but it seems like enabling the cache will deny updates of files in general. I guess i didnt find the right settings.
Eyes
Ai use "auto", works for me
KYou have a lot of control over this. When you update files, you could use the Cloudflare API to bust their cache. You can also set shorter cache lifetimes in the Cache Rules. Alternatively, if you have a database or similar and you need the new file to show up right now, store the file update time and use that the bust the cache in the URL. Alternatively again, change the key of the new file and slate the old file for deletion.
AHave been getting 403 [Error] Origin http://localhost:3000 is not allowed by Access-Control-Allow-Origin. Status code: 403
when trying to PUT to a signedUrl generated from the S3 api
I'm building it this way:
const S3 = new S3Client({
region: 'auto',
endpoint:
credentials: {
accessKeyId: process.env.CLOUDFLARE_ACCESS_KEY_ID!,
secretAccessKey: process.env.CLOUDFLARE_SECRET_ACCESS_KEY!,
},
});
const response = await getSignedUrl(
S3, new PutObjectCommand(
{
Bucket: process.env.CLOUDFLARE_BUCKET,
Key: fileName,
Metadata: {
"x-amz-meta-origin": "http://localhost:3000"
}
}
),
{ expiresIn: 3600 }
)
And this is CORS policy in R2:
[
{
"AllowedOrigins": [
"http://localhost:3000"
],
"AllowedMethods": [
"GET",
"PUT",
"POST",
"HEAD"
],
"AllowedHeaders": [
"*"
]
}
]
when trying to PUT to a signedUrl generated from the S3 api
I'm building it this way:
const S3 = new S3Client({
region: 'auto',
endpoint:
https://${process.env.CLOUDFLARE_ACCOUNT_ID}.r2.cloudflarestorage.comcredentials: {
accessKeyId: process.env.CLOUDFLARE_ACCESS_KEY_ID!,
secretAccessKey: process.env.CLOUDFLARE_SECRET_ACCESS_KEY!,
},
});
const response = await getSignedUrl(
S3, new PutObjectCommand(
{
Bucket: process.env.CLOUDFLARE_BUCKET,
Key: fileName,
Metadata: {
"x-amz-meta-origin": "http://localhost:3000"
}
}
),
{ expiresIn: 3600 }
)
And this is CORS policy in R2:
[
{
"AllowedOrigins": [
"http://localhost:3000"
],
"AllowedMethods": [
"GET",
"PUT",
"POST",
"HEAD"
],
"AllowedHeaders": [
"*"
]
}
]
AAny ETA for pre-signed POST uploads? I'm setting up an application that, unfortunately, does not support regular pre-signed URLs.
SUnfortunately I can't give you an ETA at the moment, but I can look into the status here. It may not be available in the super short-term though.
SThat isn't possible right now, but you can prefix your object names with a timestamp, and then list them perhaps?
ZHello, is R2 already stable to use custom domain with LOTS of traffic without having problems with ToS?
I had problems with this a few months ago and was wondering if everything is okay
I had problems with this a few months ago and was wondering if everything is okay
EThe 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
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.com1_2_0.chientrm.com
Ar2.cloudflarestorage.com/noti is this
