Write a proxy incident checklist by connection stage
Operators need to distinguish header rejection, pool waiting, and upstream disconnects.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Runbooks
Estimated field mix
- Site reliability50%
- Networking50%
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.
- BPROXY-101 · Document the trusted proxy chain and public origin
- BPROXY-102 · Normalize forwarded headers without accepting client spoofing
- BPROXY-103 · Strip hop-by-hop headers before forwarding requests
- BPROXY-104 · Align keep-alive lifetimes between proxy and upstream
- BPROXY-105 · Limit upstream connections per service without unbounded waiting
- BPROXY-106 · Propagate downstream disconnects through streamed responses
- BPROXY-107 · Avoid unsafe automatic replay after partial request transmission
- BPROXY-108 · Compare buffering and streaming under bounded memory
- BPROXY-109 · Reload proxy configuration without dropping healthy in-flight requests
Acceptance criteria
- Map safe failure categories to checks.
- Include current timeout and pool settings.
- Document bounded rollback and drain commands.
Implementation constraints
- Do not capture request bodies or credentials.
Verification to include
- Diagnose a synthetic stale connection.
- Distinguish pool overload from upstream application failure.
Deliverables
- Proxy support runbook.
Rollout and recovery
Ship with configuration changes and verify it during local rehearsal.
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.