Could this be the problem?
Could this be the problem?
12 Replies
Try turning HTTP/2 off on your zone
I have tried
Access to image at 'https://cdn.project-v.online/items/DLC_MP_GR_M_JBIB_6_10.webp' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Magic or idk what is it
Is there anyway I can somehow ignore this and allow access for everyone?
You can, set the allowed origins to
* to test things out
I'm unsure what your setup is like, that URL shows me DNS errorsHow can i do this?
I meant that you can set your CORS policy to this to allow all origins (it's pretty harmless if you only want GETs, but generally having an explicit allowlist is good practice):
The error I see is this:
How did you set up your custom domain?
Unplugged, plugged back in
I see that this response was cached, is it possible you've cached the non-CORS header response and so that's being sent back? Try purging your cache?
If so, your request isn't hitting R2, and so your CORS settings aren't "taking effect"
To be clear, you should use the cache, it'll help with cost and latrency, but this is a case of an incorrect thing in your cache.