The test route on the proxy Pi now points at the CMS host on port 5200.
verify-deployment.sh gets a --cms mode that checks the exact security
headers, caching, gzip only, a percent-encoded redirect, the 405 for
POST, and the CMS routes. The deploy-test job uses it once the Gitea
variable ASF_TEST_SERVED_BY_CMS is true.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The script body had been saved twice, so a production upload would have run
twice and left web.config backups on the host. Browser tests also get longer
limits on the slow CI runner; the page behaves the same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A remote of . or .. could have made the cleanup pass delete the wrong folder, so
such paths are refused before anything runs. A connection error now ends in the
normal summary instead of aborting the check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each pass is now its own lftp session with a marker in the log, so a failed
asset pass stops the script before any HTML goes up. The test checks those
markers instead of lftp's output format.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The preview server and web.config now follow the same URLs as nginx, without
the SPA fallback. Lighthouse exceptions need a recorded reason and the 404 page
is audited through an opt-in route. The deploy checks the build first and the
served result afterwards. The IIS rules stay unverified until a host exists.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>