Last I checked it was on CF because we have that Open Source Pro thing
Last I checked it was on CF because we have that Open Source Pro thing
CThis can be accomplished with Worker/R2 and a CF for Saas custom hostname
UDont think you can use workers either without having the domain on your account
HMaybe it is a layered situation, like with JSDelivr?
C@Unsmart | Tech debt Just checked, Github Pages is CDN'd by Fastly
C
Wah it's on GH Pages
UAh fair enough
Wcries in CF Pages
CUsing custom hostnames I can have any domain point to my origin and my worker handles what bucket/object is returned based on domain.
C
CUsing worker as origin
W
HHey, it’s still a meme that they aren’t using Azure CDN…
UAh yeah if you do have a domain on your CF account that could work
Cpls ask sales person to give me a £1/month enterprise deal kthx ily
CI keep getting bothered in my emails by Cloudflare Sales Agents for my personal website etc. lol
UIf you happen to have a domain on your CF account heres what you'd need to do to possibly make something work:
1: Create a worker that can serve your R2 bucket (add a custom domain my-cdn.mydomain.com)
2: Go to SSL/TLS -> Custom Hostnames and set fallback origin to my-cdn.mydomain.com
3: Click "Add Custom Hostname" enter cubity.getsharex.com
4: Set the cname of cubity.getsharex.com to my-cdn.mydomain.com
@cubityfirst
1: Create a worker that can serve your R2 bucket (add a custom domain my-cdn.mydomain.com)
2: Go to SSL/TLS -> Custom Hostnames and set fallback origin to my-cdn.mydomain.com
3: Click "Add Custom Hostname" enter cubity.getsharex.com
4: Set the cname of cubity.getsharex.com to my-cdn.mydomain.com
@cubityfirst
Wwhy do ssl for saas over just having a Worker fetching?
Woh wait nevermind
Wmy brain isn't working, i'm on holiday ok! don't bully me 
Coh hi jaex
UYeah we eventually figured that out 
C
K
EYou absolutely can change their headers with transform rules
KShould work straight away
K
C
Would this make it possible for presigned direct uploads from a frontend?KThis is for public buckets, so no
KYou can't add CORS headers to the SigV4 endpoint yet
CBummer
Sproblem of r2 bucket
S
CThat is the firewall checking your connection to the bucket
Sthis is bad, the images do not load...
UYou will need to tone down your security rules
S
UIt's not a problem with R2, you are just getting stopped by your firewall settings.
SI wish I had activated the protection and not have to go through this in the images
SI understand that I will have to create a rule for this, but you's could adjust...
UWe cant adjust your settings if you make them start blocking real people 
KThis is technically not valid CORS, but I suppose most things won’t care? Have you tried it in the wild?