A compact, non-exhaustive reference for the values that appear across the notes. Prefer the linked source for the authoritative rule; these tables are memory aids.

HTTP status codes used in release checks

CodeMeaningUsed for
200 OKThe resource exists and the representation is returnedbaseline for a healthy route
301 Moved PermanentlyThe URI changed permanentlydeciding between : old_uri and : new_uri in logs
308 Permanent RedirectNon-GET methods keep their method across the redirectthe redirects-and-status-codes note
206 Partial ContentA range request was honoredthe http-range-requests note
304 / 412Validators drive conditional requeststhe http-cache-headers note
404Not foundthe handle_errors page in the Caddyfile
500 / 502 / 503Origin or proxy failurerelease smoke tests and restart loops

Security headers seen at the public edge

HeaderA short version of the policy
Content-Security-Policydefault-src 'self'; script-src 'none' keeps the page script-free
Strict-Transport-Securitymax-age=31536000; includeSubDomains forces HTTPS for a year
X-Content-Type-Optionsnosniff stops MIME-type guessing
X-Frame-OptionsDENY prevents framing
Referrer-Policystrict-origin-when-cross-origin limits referrers

Digest commands for a released artifact

# per file
sha256sum <file>

# plain-text check available in the operator kit
check-http-headers.sh https://www.xbcatm.com/
check-tls-expiry.sh www.xbcatm.com 30

Sources