What is HTTP, and what do a request and a response look like?
Answer out loud or in your head first, then compare.
Answer
HTTP is a set of communication rules used on the internet. A client, e.g. a browser, sends a request to a given address. The server answers with a status, headers and possibly a body: HTML, JSON or a file. Headers are extra information, e.g. the content type or caching rules.
Example: the browser asks for a list of plants, and the server returns 200 and the data as JSON. HTTPS is HTTP with the connection protected by TLS. HTTP doesn't require every request to create a new network connection from scratch — connections can be reused.
Why it matters: The common foundation of REST, streaming and model integrations.
Possible follow-ups: How does a connection error differ from an HTTP 500 response?
How did it go? Be honest — “Not yet” puts the question on your review list.
Further reading
- MDN: Overview of HTTP(opens in a new tab)Accessed 22.10.2026. Requests, responses and connection reuse.