Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(wiki): document same-origin redirect confinement for admission webhooks
Vinícius DS Andrade8ee8391cead1
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex e65cba04..2ef31d5f 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -13,6 +13,11 @@ version in [`docs/changelog/`](docs/changelog/):### Fixed+- Admission webhook HTTP requests now follow redirects only within the+ configured `scheme://host:port` origin (up to 10 hops) and fail on+ cross-origin redirects without forwarding page payloads or applying foreign+ response mutations, surfacing the redirect refusal cause in logs and+ `reject`-policy errors (#1794).- Refused empty and whitespace-only `--workspace` and `--project` flags at theshared CLI scope-resolution choke point (`resolve_scope`,`resolve_scope_noting_marker_project`, `resolve_scope_with_marker`, anddiff --git a/docs/admission-webhooks.md b/docs/admission-webhooks.mdindex 7da52330..f26aeb02 100644--- a/docs/admission-webhooks.md+++ b/docs/admission-webhooks.md@@ -356,7 +356,10 @@ blocking = false # fire-and-forget afterOnly `http://` and `https://` webhook URLs are accepted; any other scheme, abare hostname, or an empty `url` fails server startup when the chain is-built.+built. Redirects are followed only when the target stays on the same+`scheme://host:port` origin as the configured `url` (up to 10 hops); a redirect+to another origin fails the webhook request without forwarding the payload or+applying any response mutation.### `blocking` (default `true`)