Document the trusted proxy chain and public origin
The application trusts forwarding headers from any caller.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- HTTP · Trust boundaries
Estimated field mix
- Security60%
- Networking40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting API sits behind a reverse proxy. Clients see intermittent disconnects and incorrect origins after changes to keep-alive and forwarding headers.
Setup prerequisites
- Create two loopback HTTP services and a local proxy with synthetic requests; no public scanning or external traffic.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List trusted proxy hops and expected public origin.
- Define which hop sets each forwarding field.
- Reject ambiguous trust configuration.
Implementation constraints
- All modeled hops are local fixtures.
Verification to include
- Resolve origin through the trusted chain.
- Reject direct-client spoofed forwarding metadata.
Deliverables
- Proxy trust contract.
Rollout and recovery
Review the trust chain before changing application origin handling.
Value of the work
For the engineer: Practice HTTP intermediaries, connection lifetimes, and network failure isolation.
For the team: Provide a proxy contract that preserves request identity and releases resources predictably.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.