FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Explicitly rejecting redirects from public RPC calls
Avoiding an unsupported runtime mode without forwarding the origin token elsewhere
Purpose
Requests from public RPCs to the database needed to avoid an unsupported redirect mode and prevent credentials from being forwarded to another destination after a 3xx response.
Implementation
Fetch now uses manual redirect handling and explicitly rejects 3xx responses as errors. The public-origin token is therefore never resent to a redirect destination, and the implementation no longer depends on an unsupported runtime mode. Structure checks reject reintroduction of that mode.
Rendering diagram…
What was confirmed
Verification results
The shared-contracts build, Web lint, type checks, 30 tests, structure checks, Worker build, and dry-run passed.
At the cutoff, responses from the production public RPC had not been verified.
Basis for completion
The work was complete when manual handling prevented credential forwarding on redirects and runtime compatibility plus structure checks were verified.