New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
image-proxy and Discord #48
Comments
Yes this is an known issue. I'm not sure what was causing it. Probably because both Discord and trace.moe are served via cloudflare, which may be blocked by some firewall settings on Discord's server side? |
What about a setting to disable image proxy and do the request client side? |
This would be blocked by browsers' security policy |
Oh duh, always forget about CORS being bad |
CORS has its own reasons for existing... and its configurable by the site :p |
Yes it's possible to load the image with CORS, but then the image would become "tainted canvas", which cannot be convereted to binary format to via toBlob or toDataURI. |
sorry, not saying it should be done. i havent checked the codebase :p |
Resolved in da5a113 ref: https://github.com/soruly/trace.moe-image-proxy (Deployed to ZEIT) |
now.sh (ZEIT, a.k.a Vercel) blocked the image proxy because it's not allowed in its fair use policy. Now switching back to cloudflare workers for the moment. Need to look for new solutions. |
image-proxy fails on discord, says "This content is no longer available"
Edit: example url for testing https://cdn.discordapp.com/attachments/473214112969654282/676078778396573706/unknown.png
The text was updated successfully, but these errors were encountered: