From f82b78bad5b71cec259e58422e44acb54a54ee69 Mon Sep 17 00:00:00 2001 From: ari Date: Tue, 20 Oct 2026 11:12:56 -0400 Subject: [PATCH] F: say what the proxy forwards instead of 'it is stripped' The caller's /api/v1 prefix is dropped during validation and the peer path is built with it, so the old sentence described half of it. --- docs/consolidator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/consolidator.md b/docs/consolidator.md index 3fb72f5..d15b47c 100644 --- a/docs/consolidator.md +++ b/docs/consolidator.md @@ -70,7 +70,7 @@ All under the inbound auth of this host; nothing is mounted while peers are off. The status object is `{name, enabled, url, server{up, since, last_checked, last_error, latency_ms}, api{up, since, last_checked, last_error, latency_ms, auth, peer_version}}`, times in RFC 3339 UTC. -The pass-through allowlist is `systemd/...`, `journal`, `journal/follow`, `docker/...`, with the query parameters the local routes accept (`state`, `unit`, `priority`, `lines`, `since`, `all`, `tail`, `follow`). A caller may include the `/api/v1` prefix; it is stripped. Anything else is a `400`, `..` and encoded slashes are rejected, `ping`, `peers/...` and `/healthz` are not reachable through it, and methods other than GET are `405`. The peer's 2xx answer comes back unchanged (status, `Content-Type`, body; SSE stays a stream) with `x-slinuxm-peer: `; every error produced for a peer carries that header too, except the `405` for a non-GET method, which the router answers before the peer route runs. Consolidated failures use the existing error shape: +The pass-through allowlist is `systemd/...`, `journal`, `journal/follow`, `docker/...`, with the query parameters the local routes accept (`state`, `unit`, `priority`, `lines`, `since`, `all`, `tail`, `follow`). A caller may include the `/api/v1` prefix or leave it out; the peer always receives the route under its own `/api/v1`. Anything else is a `400`, `..` and encoded slashes are rejected, `ping`, `peers/...` and `/healthz` are not reachable through it, and methods other than GET are `405`. The peer's 2xx answer comes back unchanged (status, `Content-Type`, body; SSE stays a stream) with `x-slinuxm-peer: `; every error produced for a peer carries that header too, except the `405` for a non-GET method, which the router answers before the peer route runs. Consolidated failures use the existing error shape: | Peer outcome | Answer to your caller | |---|---|