Cache-Control:max-age=120 this header is present in response header
Cache-Control:max-age=120
this header is present in response header
this header is present in response header
Nbecause it is giving 404 i assume it is hitting
HIf you toggle
Disable CacheCF-Cache-StatusCF-Cache-Status=HIT before disabling cache
HThat's the issue then. Cloudflare itself is caching the 404 page, meaning that you don't see the image
Nis there way to disable caching 404
Nfound way to disable cache for status code
Nthanks
Vhello all, does r2 have no egress costs at all? my company is getting fleeced by google cloud and we're looking to swap
Vcurrently comparing cloudflare and fastly, might need to add a cdn as well
Vcheers, most of it would apply except for maybe the cdn content - we primarily create photos for end users
ICloudflare allows you to connect R2 to the regular CDN which is also free up to a certain amount of traffic.
UFwiw theres no actual limit to how much data you can serve you can do as much as you want just at some level of usage they might ask about upgrading but you never have to 
At certain levels of usage it probably makes sense as a business though for other things such as SLAs
At certain levels of usage it probably makes sense as a business though for other things such as SLAs
Lis r2 traffic unlimited?
UYes
IBandwidth is unlimited and free, yes. You pay for requests, but not bandwidth.
ZThey throttle you if they detect abuse, this was a while ago though and it's by zone
ZI was never contacted about upgrading in that case
.Hey! Does anybody know if there's a roadmap / ETA for when there will be a public API to assign aliases to R2 buckets to allow public web access?
.There's an undocumented api -
But until it's made official cloudflare-go won't implement it, and until cloudflare-go implements it, terraform-provider-cloudflare won't
But until it's made official cloudflare-go won't implement it, and until cloudflare-go implements it, terraform-provider-cloudflare won't
UThat has happened in the past yes but they made a blog about how any throttles they did were a mistake and something an engineer mightve done if there was issues with the network from one customer with high usage on a specific node. I'll try to find the blog but tldr is they will not throttle customers
UHere's the blog: https://blog.cloudflare.com/how-cloudflare-erroneously-throttled-a-customers-web-traffic
The Cloudflare Blog
Today’s post is a little different. It’s about a single customer’s website not working correctly because of incorrect action taken by Cloudflare.
UA Cloudflare engineer decided to apply a throttling mechanism to prevent the zone from pulling so much traffic from their origin. Let's be very clear on this action: Cloudflare does not have an established process to throttle customers that consume large amounts of bandwidth, and does not intend to have one. This remediation was a mistake, it was not sanctioned, and we deeply regret it.
ZThey still automatically throttle you if you for example serve video through cloudflare
Zbut that's an obvious tos violation
UThey dont throttle they just block the video in that case
Znot sure about anything else other than videos
Zoh right
UCloudflare should never be throttling people and afaik only video has an auto block everything else should go through a process
Zlast words before man serves 400 petabytes of his linux isos:
Zfrom r2?
Zare you attempting to proxy a custom domain?
Zi.e:
Zis that what's going on?
Zohh
Zare you proxying the record?
Zsure
Zthat'd be helpful
Zah
Ztry disabling proxy
Zthen wait a couple of minutes, and see if it works
Zyou may need to do a refresh (or equivelant) in tebex's dashboard as well, so that it properly issues an SSL cert (not really sure how their system works)
Ztebex didn't tell you to proxy it, right?
Zokay
