Clarify plan: ServeMux patterns are a Go-1.22-era stdlib feature, project stays on Go 1.26
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -391,7 +391,10 @@ pods would refuse connections while still being Service endpoints. The 1-replica
|
|||||||
constraint comes from lease state being per-process, which the spec already accepts —
|
constraint comes from lease state being per-process, which the spec already accepts —
|
||||||
both facts go in the README caveats.
|
both facts go in the README caveats.
|
||||||
|
|
||||||
stdlib `http.ServeMux` with Go 1.22 method+wildcard patterns:
|
stdlib `http.ServeMux` using its method+wildcard patterns (`"GET /path"`,
|
||||||
|
`"/{id}"` + `r.PathValue`) — a stdlib feature available since Go 1.22, used
|
||||||
|
here so no third-party router is needed; the project itself stays on the
|
||||||
|
pinned Go 1.26:
|
||||||
`GET /v1/proxies`, `POST /v1/leases`, `DELETE /v1/leases/{id}`,
|
`GET /v1/proxies`, `POST /v1/leases`, `DELETE /v1/leases/{id}`,
|
||||||
`POST /v1/leases/{id}/report`, plus unauthenticated `GET /healthz`.
|
`POST /v1/leases/{id}/report`, plus unauthenticated `GET /healthz`.
|
||||||
Middleware outermost-first: recover → request-log → `MaxBytesReader(64KiB)` → bearer
|
Middleware outermost-first: recover → request-log → `MaxBytesReader(64KiB)` → bearer
|
||||||
|
|||||||
Reference in New Issue
Block a user