clawbot a7bb770e60 Answer image requests with 503 in maintenance mode (closes #71) ...

maintenance_mode was only reported by the health check; every request
was still served. One middleware in routes.go, applied to /v1/image/
and /v1/e/ only, now answers them with 503, a Retry-After of
MaintenanceRetryAfterSeconds and the JSON error body while it is on.
It calls Server.MaintenanceMode(), which had no caller.

The health check stays 200 and reports maintenance_mode: the image's
Docker HEALTHCHECK requests it, a 503 there would make the container
unhealthy, and upaas marks a deploy failed when its container is
unhealthy. The login and URL generator pages and /metrics keep working.
Documented in README.md and config.example.yml.

Model: opus-5-5

2026-09-29 05:10:06 +00:00

..

http_internal_test.go

Harden http.Server: slowloris timeouts and form body limit (closes #92)

2026-09-21 20:59:24 +02:00

http.go

Harden http.Server: slowloris timeouts and form body limit (closes #92)

2026-09-21 20:59:24 +02:00

login_rate_limit_internal_test.go

Test that maintenance mode refuses image requests (closes #71)

2026-09-29 05:10:06 +00:00

maintenance_internal_test.go

Test that maintenance mode refuses image requests (closes #71)

2026-09-29 05:10:06 +00:00

routes.go

Answer image requests with 503 in maintenance mode (closes #71)

2026-09-29 05:10:06 +00:00

server.go

next -> main (1.0.0 milestone) (#105)

2026-09-21 09:31:54 +02:00