frame-src gets the three exact Friendly Captcha global hosts (no wildcard).
When the widget errors, is blocked or shows no sign of life, the form says so
and offers the mail button instead of blocking silently. Adds an e2e for the
form with a mocked API, a draft privacy text for approval, and label tests.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The check now fetches real admin files (index.html, favicon, the css and
js from the served index) and an unknown admin file. A POST with an empty
body returns 405; without a body the HTTP/1.0 proxy hop answers 400.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
Plain map keys compare case-insensitively, so /Over-Mij was not redirected. A
path starting with an encoded backslash could become an open redirect through
the trailing-slash rule; it now gets the 404 page. Also makes the tests readable
for nginx's workers and less sensitive to the slow CI runner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pages now map to their html file, other forms get one redirect, unknown URLs
get a real 404 and responses are compressed. A browser-free test suite runs the
rules against a real nginx, in CI only so far.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
IIS now sends www.andreaslop.nl to https://andreaslop.nl in one step, so
monitoring and search engines see a single address. The go-live steps check
the redirect and wait for the privacy statement, and the readiness checklist
lists what is left for the go-live.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sentry loads after the page and reports errors only, without personal data;
Umami counts visits per environment. Both only run on andreaslop.nl and
test.andreaslop.nl. The CSP allows just these two hosts, and builds carry the
commit SHA as release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first render with axe takes up to 7 s on the Raspberry Pi runner,
above Vitest's 5 s default; the suite now allows 20 s per test. Also
silences the router warning in the test that crashes a page on purpose,
and makes the nginx test config return 404 instead of a redirect loop
(500) while the test folder is still empty.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pipeline runs lint, format, tests, build, dependency audit and
Lighthouse (mobile and desktop, Playwright Chromium on the arm64 runner)
on every pull request, push to master and manual run.
Pushes to master deploy to test automatically, and any branch can be
deployed to test manually. Test is a Raspberry Pi with nginx next to the
current WordPress site; the deploy refuses folders containing WordPress.
Production deploys are manual and only from release/* branches, over
FTP with TLS to the IIS webhost.
The IIS web.config and both nginx configs are generated from the same
security header list as the Vite servers, with a test that fails when
the generated files drift. Adds .gitattributes for LF line endings and
pins pnpm through packageManager.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>