Greasy Fork镜像

Hello, first off, fantastic script! It's been very helpful.

I wanted to report a specific bug regarding the overlay import feature. When I use a link from media.discordapp.net, the import process fails and I get a 404 error in the console, even though the link is active and working.

Steps to Reproduce:

• Get a direct link to an image hosted on Discord's CDN (media.discordapp.net).
• Try to import it into the script.
• Observe the console error:

  Import failed for https://media.discordapp.net/...
  Error: GM_xhr failed: 404

Key Observation:

The URL provided is 100% valid. If I copy the URL from the error message and paste it into a new browser tab, the image loads correctly.

Technical Analysis:

This behavior strongly suggests a Cross-Origin Resource Sharing (CORS) issue. My theory is that Discord's servers are intentionally blocking the script's GM_xmlhttpRequest. The request from the userscript is likely missing the authentication cookies and standard browser headers that are present when I visit the URL directly. Instead of returning a 403 Forbidden error, Discord's server returns a 404 Not Found as a security measure to obscure the resource's existence from unauthorized scripts.

The problematic code seems to be in the gmFetchBlob function, which makes a "vanilla" GM_xmlhttpRequest without any custom headers.

Suggested Solution:

This typically requires routing the request through a proxy server. The script would send the Discord URL to the proxy, and the proxy would fetch the image and return it to the script, thus bypassing the browser's cross-origin restrictions.

Thanks again for all your hard work. I hope this detailed report is useful for debugging!

I appreciate you taking the time to reply, but there's no need for that level of hostility. My only intention was to provide a detailed report to help improve the script.

To be clear, I used an AI tool to help structure my findings and ensure the English was clear, but the issue itself is real and I tested it myself.

Regarding your technical points:

1. Link Expiration: The link was freshly generated and tested immediately. It was 100% active.
2. Caching: I specifically tested the URL in a new incognito tab to ensure it wasn't a cache issue. The image loaded fine.

The core problem remains: GM_xhr receives a 404 for a URL that is demonstrably live and accessible to the browser. Whatever the underlying cause is—whether it's headers, referrers, or something else Discord's CDN is checking for—it's a reproducible bug. I was hoping to help pinpoint it.