Pitch1 Full-Time Browser vs cURL Test

This page makes no Full-Time request just by loading it. Each button below makes one server-side test request from this UK server.

Target: https://fulltime.thefa.com/index.html
Chrome/Chromium found: NO
proc_open available: yes

No browser executable was found. The cURL comparison can still run, but the important browser-stack test cannot run on this server unless Chrome/Chromium is installed.

1. cURL comparison

This should reproduce the sort of request that is currently returning 403.

2. Chromium/Chrome test

This launches an actual browser process on the UK server and asks that browser to load the same Full-Time homepage. This is the useful test for separating a cURL/request-fingerprint problem from an IP/network-level block.

How to read the browser result:

If cURL is 403 but Chromium gets the normal Full-Time page, the UK IP itself is not blanket-blocked; the cURL/request fingerprint is the problem.
If Chromium also gets a block/403 page, that is much stronger evidence that Full-Time is rejecting the UK server/IP/network rather than merely PHP cURL.

Each test type is locally limited to once every 15 minutes to avoid accidental repeated requests.