noCV
BPROXY-104 · Manage connections

Align keep-alive lifetimes between proxy and upstream

Practice briefBugAdvanced

The proxy reuses sockets just after the upstream has closed them.

Focused work estimate
3h + prerequisites
Priority in the scenario
High
Engineering practice
Connection pooling

Estimated field mix

  • Networking60%
  • Performance engineering40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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.

Use in my work boardView project and downloads

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

  • Document idle-timeout relationships.
  • Retire idle connections before unsafe reuse under the chosen policy.
  • Classify stale-connection failures separately.

Implementation constraints

  • Use controlled local timeout fixtures.

Verification to include

  • Reuse a valid connection.
  • Expire upstream idle state and verify bounded recovery.

Deliverables

  • Connection lifetime configuration.

Rollout and recovery

Change one timeout at a time; retain previous values for comparison.

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.