What extra care do streaming responses need in middleware?
PICTURE THIS: A REST CALL
Simple meaning
StreamingHttpResponse content is an iterator consumed later
WHY — Middleware instead of guessing?
Why interviewers care about Middleware:
who only read docs from people who shipped.
and tied to Python work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1StreamingHttpResponse content is an
iterator consumed later
- 2reading it in middleware
exhausts the stream for the client.
- 3Wrap or tee only
if you must, and prefer setting headers without touching .content.
- 4Gzip middleware and similar
wrappers have historically been tricky with streams.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
StreamingHttpResponse content is an iterator consumed later reading it in middleware exhausts the stream for the client.