Edit: I just want to preface this by saying
image/thumbnail loading works perfectly fine from my same IP when using any Chromium-based browser. This appears to be an issue related to Firefox's "Opaque Response Blocking" (ORB) policy in reaction to receiving an
.
In Mozilla Firefox, can't load any goonbox/cuckcapital images unless the cuckcapital .JPG is directly loaded in its own new tab without any referer (Doesn't load images regardless of ublock origin/umatrix/FF built-in Tracking Protection being enabled/disabled). Here is the URL I was testing from:
https://goonbox.cr/img/t2IWpU5
If I click "download image", I get this:

If I copy the jpg URL (
https://simp6.cuckcapital.cr/images4/29ebf49d-5622-4cb9-a5b6-c6621db4816c.jpg ) from the "Download Image" page, I can load it by pasting it into its own new tab. However, since Cloudflare returns "no-cache" in the response header, I can't just go back to goonbox, hit refresh, and expect my local cache copy to show up on that page after loading the image directly on its own tab.
----- AI response below (
I don't know if this is helpful at all ) -----
The issue is that
simp6.cuckcapital.cr is rejecting cross-origin requests from goonbox.cr by serving a 403 JSON error instead of an image file, which triggers Firefox's strict
Opaque Response Blocking (ORB) policy.
Here is a summary of the exact changes the engineer can make, categorized by where they need to apply them:
Option 1: Changes on
(The Image Host — Recommended)
This is the most effective place to fix the issue. The image server needs to tell browsers that
is allowed to embed these files.
- Add CORS Headers: Configure the web server (Nginx, Apache, or Node.js) hosting the images to allow cross-origin requests from the front-end site. It needs to send these headers with every image response:
http
Code:
Access-Control-Allow-Origin: https://goonbox.cr
Access-Control-Allow-Methods: GET, OPTIONS
- Fix Fallback MIME-Types: Currently, when a request fails or is restricted, the server responds with
Code:
Content-Type: application/json
. The engineer should change the server behavior so that if a request fails, it serves a standard fallback image (like a
or
) with a proper
or
MIME-type. This stops Firefox from triggering the ORB security block.
Option 2: Changes on Cloudflare (The Security Layer)
If
uses Cloudflare, Cloudflare's
Hotlink Protection or
Web Application Firewall (WAF) is likely generating that
JSON error page.
- Create a WAF Skip Rule: The engineer should go to the Cloudflare Dashboard for
and navigate to Security > WAF > Custom Rules. They can create a rule that allows requests coming from GoonBox:
- Field:
or
- Operator:
- Value:
- Action:
(Hotlink Protection / Managed Rules)
- Adjust Hotlink Protection: If they have the global "Hotlink Protection" toggle turned on under Scrape Shield, they can turn it off and replace it with a custom firewall rule that explicitly whitelists trusted domains like
.
Option 3: Changes on goonbox.cr (The Front-End Website)
If the engineer only controls the front-end site (goonbox.cr), they can force the browser to omit tracking headers so the image host doesn't realize the request is cross-origin.
- Apply a Global Referrer Policy: Add a <meta> tag to the <head> of the website to instruct the browser never to leak the origin trail to image elements:
html
Code:
<meta name="referrer" content="no-referrer">
- Update Image Tags Individually: Alternatively, they can append the referrerpolicy attribute directly to the HTML image tags that load from that server:
html
Code:
<img src="https://cuckcapital.cr" referrerpolicy="no-referrer">
Note: If Cloudflare is checking advanced metadata like
Code:
Sec-Fetch-Site: cross-site
, this front-end trick alone might not work, making Option 1 or Option 2 much more reliable.