So CORS rules aren't _cached_, they're distributed globally like all other CF config, and so we don'
So CORS rules aren't cached, they're distributed globally like all other CF config, and so we don't promise strong consistency there
HNo, I meant that it was cached on the Response via the CF Cache. But now I don't remember if R2 public domains even have cache...
SThey don't, out of the box. That's one of the reasons why we encourage you to use a custom domain, so you can configure whatever makes sense to your app
H#1: Not at the moment
#2: Caching is free on Cloudflare. The max size for a cached object is determined by the plan that the custom domain has.
#2: Caching is free on Cloudflare. The max size for a cached object is determined by the plan that the custom domain has.
SYou can request adjustments to limits that conflict with your project goals by contacting Cloudflare. To increase a limit, complete the Limit Increase …
HHappy to help!
HJust to clarify, because I misspoke, the max size for a cached object is determined by the plan that the custom domain has, and it isn't applied across your entire account.
Jwhat's the expected behaviour when making a range request on something in R2 with caching enabled?
Jcurrently the requests completely stall if the cache is cold
Jit's been about 20 minutes since I enabled caching on my custom r2 domain, and any range request that doesn't start at byte 0 still just stalls indefinitely
KCan't replicate it personally - do you have a URL to hand?
JJwhich is a 700MB file
HDepends on the tier
Jwhere are the cache size limits described?
JI'm on the free tier
Jshouldn't files that exceed the limit be served uncached?
H100 MB
Jthanks, I'll look into chunking it
Jbut I'm still concerned that it behaves like this
HNever mind:
Jif the resource isn't cached, it just breaks
HThat shouldn’t be an issue. It will be slower, but it shouldn’t break
Jit is, the requests just stall indefinitely
Ja range request for bytes works fine, but a range starting at any other point breaks completely
HJyep
Jthis seems to be a bug in how CF handles range requests
Jassuming this isn't how it's supposed to behave
HIt does render? Because the map should use Range requests to render
Jyes it renders fine
Jand my site works fine if I disable "cache everything"
Jis it possible to have more than one custom url pointing to the same bucket?
Joh yes, I can just do that through the web interface, just can't use a CNAME to point at it
Jis this a project that uses range request against a larger file served on CF to serve map tiles?
Jit seems to use a worker
Jnot exactly sure what bit of the project I'd look at
HI actually used Protomap in the map above, so if that didn’t work, it probably wouldn’t work for you either
H^What they did there
JI actually just realised I had this problem half a hear ago
Jand had my ticket escalated
Jbut it didn't go anywhere, support just kept asking if it was still a problem
JI just reopened the ticket.. will see if it goes anywhere