What is the POST-redirect-GET pattern?
PICTURE THIS: DJANGO MVT
Simple meaning
After a successful POST I redirect to a GET page so refresh does not resubmit the form.
WHY — Architecture instead of guessing?
Why interviewers care about Architecture:
who only read docs from people who shipped.
and tied to .NET MVC 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:
- 1After a successful POST
I redirect to a GET page so refresh does not resubmit the form.
- 2TempData can carry a
flash message.
- 3How it works
It prevents duplicate creates.
- 4Give an example
One tiny concrete case you can say aloud.
- 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
After a successful POST I redirect to a GET page so refresh does not resubmit the form. TempData can carry a flash message.