Why is the Glitch CDN not Cross Origin?


#1

Why is the Glitch CDN not Cross Origin?
https://cdn.glitch.com/28c8b052-7a39-4169-9818-6f8d44e76fdd%2FLevel.png?1545863360742
tells me my canvas is tainted while
https://i.imgur.com/cYBxGNp.png
does not. I want to use the CDN and not Imgur, but if there is a good reason why it is not Cross Origin, then I will have to use Imgur, as they act as a de facto image CDN.
P.S. Never mind, if you access the image too much it doesn’t work, I can use https://cors.io/?

Unneeded Fun Fact - While researching, I learned that https://developer.mozilla.org/en-US/docs/Web/HTML/CORS_enabled_image uses Glitch’s cdn in one of their examples. They also apparently give a tutorial how to circumvent stuff like this in practice by using an express app. I want to keep mine a non-server based app anyway, though. https://cors-image-example.glitch.me/


#2

Never mind, I just realized that the example I found on mozilla actually uses a (I think) client-side technique, although I wish it was more like Imgur where you can just automatically have it. For some reason it uses an express server.
tl;dr doesn’t change too much, although now I have another option.
EDIT: https://cors.io/ is probably sufficient for now, but I would rather not have to use it.
EDIT 2: https://cors.io/ does not work after a period of time for some reason, whoops.
By now I have a theory that the asset can’t be called many times over a period of time, though it doesn’t appear to change when I just refresh it a bunch.
EDIT 3: Except my theory is broken by the fact the imgur also switched from being CORS to not after several requests as well. This could be a general feature of servers, idk by now.

EDIT 4: My newest theory on cors.io is that it does not send images with the correct headers :frowning:, so I would either have to make an xhttp request or find a different site.


#3

NEVER MIND ON ALL OF THIS
I’M A HUGE NOOB
I REALLY JUST NEED
crossorigin=“anonymous”