What is HTTP and how does a browser talk to a MERN API?
PICTURE THIS: A REST CALL
Simple meaning
HTTP is a request-response protocol.
WHY — HTTP instead of guessing?
Why interviewers care about HTTP:
who only read docs from people who shipped.
and tied to Full Stack 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:
- 1Define it
HTTP is a request-response protocol.
- 2The client sends a
method, URL, headers, and optional body
- 3the server replies with
a status, headers, and a body.
- 4In a MERN app
the React client typically exchanges JSON with an Express API over HTTP or HTTPS.
- 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
HTTP is a request-response protocol. The client sends a method, URL, headers, and optional body