This is a continuation of a thread called Images or URLs. It’s become more a question of how and why CORS is an issue in Bubble. Specifically it seems that if you do all your image handling with the Image Type there doesn’t seem to be a CORS problem. And yet if you change an Image to a URL it causes CORS errors in the browser. The question is WHY? When they are both referring to the same files in AWS storage.
I have a plugin that works fine with URL’s from free origin sites but throws CORS errors with URL’s like https://s3.amazonaws.com/appforest_uf/f1550114021755x553548118126321540/paint-eb3cb90a2d_1920.jpg. Not surprising.
But, as I understand it, Bubble stores everything on AWS and so shouldn’t it share the same origin?
How do Image Types avoid cross origin issues in Bubble?