Does R2 support anything above Upload Concurrency 2?
Does R2 support anything above Upload Concurrency 2?
SIt should now! I've done tests with up to 70
Kiirc the notice about multipart concurrency was removed awhile ago
Kyeah that
HWeird. Mine freezes above 2. This is it with 3:
HWith two it runs at about 2 MB/s, but it runs
HAnd my current connection is rated for about 400 MB/s, so it shouldn't be a network bottleneck...
JStrange.. I have my bucket public and exposed via a subdomain, and I then added my main domain as the allowed domain in the CORS settings, but I'm still getting CORS errors
SIt just... doesn't make any progress? I'd expect you to see 429s or something if it is too high..
HActually, same on this one. Does it matter that I changed the config through the Dash?
HNo errors or anything. It just gets stuck
SSomeone yesterday was saying the same thing. CORS config is eventually consistent but it shouldn't take too long
HIt's been about a day for me: https://pub-0177eb9df0874e6e892a9e84263b9075.r2.dev/sprites.json. Just to make sure though, it should send
ACAOOPTIONSTry adding a
-vv
DSame here, I've added an origin yesterday and cors headers are still not present on the actual response
HJI tested the url here and it seems to be fine https://cors-test.codehappy.dev/?url=https://data.infinitenovelty.com/db.4.sqlite&origin=https://infinitenovelty.com&method=get
Jbut when actually trying to load the file on my site it gives the CORS error.. https://infinitenovelty.com
J
SIt should, yep
SYeah on that CORS testing site I see a warning, so this does look like an issue
Jisn't that just saying that I have an explicitly allowed domain?
Jwhich is fine, I have one domain where the resource will be used
SYeah NVM I'm an idiot, I thought this meant that this header was missing (when I should have read the line right above the code block)
JAh, figured it out, I needed to allow HEAD!
SFor others who were seeing similar CORS issues, I'm guessing y'alls config is correct, right? 
SThis one seems to be working fine for me as well now!
Jthe problem is, devtools doesn't tell you what kind of request is being made if there is a CORS error
SThe Network tab should, no?
J
K
KOne of the queries that Synology makes results in a
NextMarkerHere's what I get for headers, live, with cache disabled locally: Is it maybe that it is cached without the CORS headers?
SSo 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?