3 Commits

Include renames

Author	SHA1	Message	Date
sneak	afe6e60b9e	Render admin page errors in the normal layout (closes #382) ... Every 400, 403, 404 and 500 on an admin page now answers with an error page in the normal layout: one fixed line for the status and a link back to the webhook list, or to sign-in when nobody is signed in. The router's handler for unknown paths, the CSRF middleware's refusal and a panic in an admin page route group use the same page; each such group has its own recoverer and error reporting for that. The page always sends Cache-Control: no-store. Status codes are unchanged. The receiver, the healthcheck and /metrics keep their plain answers. If the error page fails to render, the answer is the same status in plain text; if it panics, the answer is a 500. Model: opus-5-5	2026-10-02 05:27:22 +00:00
clawbot	f0adeafde3	Drop Set-Cookie from the recovered 500 (closes #193) ... When a handler sets a cookie and then panics before sending anything, the recover middleware now deletes Set-Cookie before writing its 500, so a request that failed never hands the client a credential. Every other header, Location included, is left as http.Error leaves it, matching chi's Recoverer. A response that was already sent is untouched. Tests cover the uncommitted case (no cookie, Location kept) and assert the cookie still reaches the client when the response was committed before the panic. Model: opus-5-5	2026-09-29 10:30:26 +02:00
clawbot	33e4fa4faa	Report handler panics through the logger and answer 500 (closes #187)	2026-08-18 08:33:12 +02:00