Answer HEAD requests and give 405 a plain message (closes #111) #136

Merged
clawbot merged 1 commits from issue-111-head-requests into next 2026-10-20 03:06:23 +02:00
1 Commits
Author SHA1 Message Date
clawbot db4f58d737 Answer HEAD requests and give 405 a plain message (closes #111)
check / check (push) Waiting to run
Every route was registered for GET only, so HEAD answered 405, and on
the JSON routes that 405 said "Internal server error". chi's GetHead
now serves HEAD with the GET handler; /ip and /ip/ register HEAD
themselves, as GetHead does not reach them. The /api/v1 and /ip route
groups answer a path they lack with a JSON 404 "Not found", and the
other methods the router knows (POST, PUT, PATCH, DELETE, OPTIONS,
TRACE, CONNECT) with a JSON 405 "Method not allowed" whose Allow header
names GET and HEAD. JSONValidationMiddleware gives a 4xx sent without a
JSON body the status's standard text instead of "Internal server error".

Model: opus-5-5
2026-10-20 00:56:41 +00:00