Strip hop-by-hop headers before forwarding requests
Connection-specific headers are forwarded as if they were end-to-end metadata.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- HTTP semantics
Estimated field mix
- Networking80%
- API design20%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Remove declared hop-by-hop fields.
- Honor fields named by the Connection header.
- Preserve required end-to-end headers.
Implementation constraints
- Parse header names case-insensitively and bound header size.
Verification to include
- Forward a valid request unchanged semantically.
- Verify Connection-nominated fields do not reach upstream.
Deliverables
- Header forwarding tests.
Rollout and recovery
Deploy to the local proxy fixture first and inspect resulting headers.
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.