Enforce response byte limits during streaming
A response exceeds memory limits before its declared size can be checked.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Streaming · Resource bounds
Estimated field mix
- Performance engineering40%
- Security30%
- Networking30%
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 content-import service accepts document URLs. The team needs explicit destination approval, redirect handling, and response limits before enabling imports.
Setup prerequisites
- Create a local HTTP destination simulator and DNS double with authorized address cases; contact no real external hosts.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Enforce streamed compressed and expanded byte limits.
- Abort when the configured bound is exceeded.
- Reject inconsistent length metadata safely.
Implementation constraints
- Never buffer an unbounded response.
Verification to include
- Fetch a small valid synthetic document.
- Abort an oversized or expanding response and release resources.
Deliverables
- Bounded response reader.
Rollout and recovery
Start with conservative document limits and explicit too-large errors.
Value of the work
For the engineer: Practice URL interpretation, network policy enforcement, and resource controls.
For the team: Provide a reusable fetch boundary that makes destination authority and failure behavior inspectable.
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.