requests Library: Redirect with a Consumed Stream

Bug SquashStripeLast reported June 2026Medium Frequency
Reported
5× across candidate reports
First seen
April 2025
Last reported
June 2026
Reported outcome
mixed

Problem Overview

You are given a repository implementing a custom HTTP requests library (similar in spirit to Python's requests). Two test cases are failing, both involving 301 redirects with streaming data (one with a file stream, one with binary data). The symptom is that reading response content during or after a redirect…

  • 2 candidate-reported follow-ups — the exact probes interviewers asked, with the trigger for each
  • The rest of the problem statement — full requirements, constraints, and edge cases
  • Approach and trade-offs — what passing candidates did, and the mistakes that sink people
Unlock the full Stripe catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Stripe question.
Unlock with Pro
Already a member? Sign in
Verified Source
Every question is reconstructed from multiple independent candidate reports. Verbatim follow-ups, not invented ones.
Codex Fact-Checked
Technical claims, formulas, and scale numbers are reviewed against primary sources.
Interviewer Follow-ups
The exact follow-ups reported by candidates, with the trigger that prompts each one — plus the mistakes that sink people.
Is this helpful?