So, after a bit of testing with the example from the super-fetch-plugin, I’ve tried different kinds of websites and it worked, including a URL from comments-plugin.perchance.org, which I got from inspecting a comments plugin iframe from the DevTools. But in this case, not from user-uploads.perchance.org, it kept having the same CORS issues just like the ordinary fetch function. Specifically I wanted to get a text content from a file mentioned in the huge-emoji-list pack.
I think it’s a very neat concept when we could “superfetch” a content uploaded from https://perchance.org/upload right from any generator, but at least, that’s I’m getting for now.
Sorry about that - this has randomly happened to me a few weeks ago too. I think an erroneous response is getting cached in the browser sometimes. I’ve added a fix so this won’t happen with super-fetch-plugin. Previously perchance upload URLs were skipping the proxy because it’s actually not needed (perchance uploads allow normal fetch from perchance generators), but due to this cached error thing I’ve made it so it falls back to using the proxy if there are any issues with a normal
fetch. I’ll hopefully get a chance to look into the root cause soon.TL;DR: It should work fine now, regardless of the browser caching the rare error responses. Thanks for the bug report! Thought it might have just been something weird with my browser, so I didn’t fix it when I came across it.
Thanks! The CORS error is still happening on my primary Edge profile, but now the fetching worked out anyways.
I was able to fetch it with the super fetch here: https://perchance.org/4cozwe59pi
I also didn’t have any CORS problems.
I still got the CORS error on my Edge browser, but it did end up fetching successfully on Firefox without any errors.
I’m also on Edge and no CORS issue … weeeeiirdd. I’ve also tried it in a profile without extensions (to see if any of my extensions messes with it) but it also goes through no problem. Same with Google Chrome, Firefox, Opera GX, and Opera Normal.
I also once tried it on Edge on mobile and a private window on Edge on PC and both did fetch successfully.
