UPLOAD THIS ALONGSIDE THE FIRST TEST

Extract the ZIP in the document root for fmovies-to.co. It creates relay-test-v2.
It does not replace the original relay-test folder, homepage, or .htaccess.

First open:
https://fmovies-to.co/relay-test-v2/diagnostics.html
Click Check both loaders once.

Then open:
https://fmovies-to.co/relay-test-v2/index.html
Wait for Ready, click Load test ads, and test the popup once.

Keep your intended AdBlock/AdGuard settings active. Tell Codex when uploaded so it
can run the live checks. PHP 8.0+, cURL and PHP PATH_INFO are still required.

CHANGES
- Removes the application-specified Content-Length. The hosting stack determines
  the final response length after compression. Incorrect compression/length is a
  documented possible cause of unbranded Cloudflare 502 responses, but the cause
  on your hosting has NOT yet been confirmed.
- Treats empty script bodies as failure instead of a misleading successful load.
- Detects the observed provider proxy rejection in popup responses and reports
  failure rather than displaying it as a successful relayed ad page.
- Adds fixed-route diagnostics returning MIME type, size and rejection/error
  categories without executing or publishing provider code or visitor identifiers.
- Preserves the fixed upstream placements, public-IP pinning, TLS verification,
  request limits and relay-first loading. No provider cookie or visitor-IP spoofing.

This package is a tested response-handling correction and diagnostic experiment.
It is NOT a verified solution to the provider's proxy rejection. The actual click
flow must be retested after loader initialization. No change of domain or response
header can guarantee that the provider accepts a server-originated request.
Cross-site embedding and credited impressions/revenue remain unverified.

Diagnostics return HTTP 200 to deliver their report even when the upstream fails.
Read upstreamFetchCompleted, bodyBytes, contentType, providerProxyRejection and
error; a successful report transfer does not mean the ads work.

The public diagnostic page uses the relay's fixed routes and per-IP request limits.
It is for this controlled test, not a general-purpose fetching service. Do not
share unredacted query strings or access logs. Restrict the test folder after use.

Reference for the response-handling hypothesis:
https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-502-504/

LOCAL VALIDATION
PHP syntax checks passed. The unchanged core passed its 35 existing checks.
Seven gateway scenarios passed using deterministic upstream fixtures with PHP
output compression enabled: usable script, empty script, proxy rejection, upstream
failure, and successful/failed diagnostic reports. The browser diagnostic also
fetched two nonempty real provider scripts from the LOCAL network. These checks
do not prove behavior from the hosting server or solve its proxy rejection.