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>
On the catch-all 404 page the router shows its pending copy for 500 ms while
the server copy stays hidden with display:none. The test counted h1 elements in
that window and found the hidden one on the faster PC runner. It now counts what
a visitor or screen reader gets, then checks that the hidden copy is gone.
Co-Authored-By: Claude Opus 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 must behave like the real server, or Lighthouse and the
browser tests prove the wrong thing. The tests also cover the new URLs in a real
browser: one redirect, one title, a clean hydration.
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>
Real nginx passes all 134 server rule tests in CI. The seven remaining failures
were tests cut off at 60 seconds on the Raspberry Pi.
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>
Lazy loading saved its bytes during page load, but left the logo empty for a
moment when navigating to the homepage on a wide screen. Also adds the second
unit's code summary and the shared docs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tests cover every page without JavaScript, the menu by keyboard and pointer,
the fade-in at load and on scroll, and image requests per width. They found that
the closed menu's shoot links could take focus, which is fixed here.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The prerendered 404 page is served for other URLs, so its dehydrated match id
differs and the router renders the catch-all's pending component first. Without
one that render was empty, which gave React error 418 and duplicate head tags.
The tests run the built output in a real browser under the production CSP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>