stegod10
03/09/2023, 10:33 AMstegod10
03/09/2023, 10:34 AMSkye
03/09/2023, 10:39 AMstegod10
03/09/2023, 10:41 AMSid | R2
03/09/2023, 11:24 AMAdvany
03/09/2023, 12:17 PMAdvany
03/09/2023, 12:19 PMEpailes
03/09/2023, 12:21 PMAdvany
03/09/2023, 12:23 PMErisa | Support Engineer
03/09/2023, 1:05 PMCyb3r-Jok3
03/09/2023, 1:53 PMJacob | Pages
03/09/2023, 2:17 PMAdraas
03/09/2023, 2:29 PMkian
03/09/2023, 2:30 PMkian
03/09/2023, 2:30 PMDELETE
causing itAdraas
03/09/2023, 2:30 PMAdraas
03/09/2023, 2:30 PMAdraas
03/09/2023, 2:31 PMkian
03/09/2023, 2:31 PMkian
03/09/2023, 2:31 PMAdraas
03/09/2023, 2:35 PMsilentdevnull
03/09/2023, 4:24 PMFleetwood
03/09/2023, 4:57 PM.dev
domain, you can simply make a get to r2.dev/{bucket}/{fname}
and you're away. With a custom domain this seems not to be the case.kian
03/09/2023, 4:57 PMkian
03/09/2023, 4:57 PMFleetwood
03/09/2023, 4:57 PMr2.dev/{fname}
for exampleFleetwood
03/09/2023, 4:57 PMFleetwood
03/09/2023, 5:02 PMJon @ Transistor
03/09/2023, 7:16 PMpreflight
request is always 403ing. it's an OPTIONS type request, and I'm not entirely sure how to get those working? Browser console is showing Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I have set up the CORS policy for the bucket with "AllowedOrigins": ["*"]
kian
03/09/2023, 7:18 PM