Add an integration response-header hook #782
Description
Update, 7 October 2026. The hook is not in the module series (#1043 to #1094). An earlier version of the documentation set (#1047) added IntegrationResponseMutator, and it was taken out because no integration used it and the series' rule is against surface nothing uses. The hook returns with the first integration that needs one, and its design, 2026-07-30-integration-response-header-hook-design.md in #1342, is the starting bar for that work.
Description
Integrations can rewrite the HTML body today but cannot set headers on the outbound response. Add an IntegrationResponseMutator hook applied to the platform-neutral http::Response at the response convergence point, so an integration can add response headers, for example to request additional client evidence on a later request. This is a host-neutral extension point alongside the existing body-only HTML processing.
Done when
- An
IntegrationResponseMutatortrait and registry wiring (response_mutators,apply_response_headers). - Each adapter applies registered response-header mutations on the outbound response.
- Covered by tests.
References
- Part of Pluggable, competition-neutral modules with a technical permission model #777. Not implemented by the module series, as the update above says.
Activity
Address review: close identity/privacy gaps in the provider and permi…
jwrosewell commentedon Oct 12, 2026
Update. Still not in the stack. Page changes as middleware (fork pull request 5, jwrosewell#5) replaces the four page hook traits with one contract that changes the body alone, and a response's headers stay the adapters' finalize step's, so this hook returns with the first module that needs one, as the 7 October update says.