FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Applying redirect rejection to public RPCs
Preventing credential forwarding with runtime-compatible manual handling
Purpose
The public RPC redirect boundary needed to be applied to the database connection code used by the actual Web runtime.
Implementation
Manual redirect handling and explicit rejection of 3xx responses are now applied to the public database client. The origin token is not forwarded to another destination, and structure checks reject reintroduction of the unsupported mode.
The public database client diff shows the boundary that disables automatic redirect following and explicitly rejects 3xx responses. Manual handling and status validation stay in the same function so an origin credential carried by the request is not sent to another destination.
Rendering diagram…
What was confirmed
Verification results
Web linting, type checks, 30 tests, structure checks, the Worker build, and dry-run passed.
At the cutoff, recovery of production public RPCs and their external responses were not verified.
Basis for completion
The work was complete when the no-forwarding redirect boundary was applied to public RPCs and passed runtime-oriented checks.