Back to the study

Learning term

HTTP response — Web fundamentals

HTTP response: The server reply containing a status code, headers, and optional payload. This card shows its role in “Web fundamentals” and a safe diagnostic path.

Web fundamentalsLevel 0–3

Orientation

HTTP response: The server reply containing a status code, headers, and optional payload. At this level, separate purpose, input, and visible result. Place HTTP response within Web fundamentals before changing settings or files.

Exercise

Try it safely

When a web request fails, use `curl -v` to preserve the method, URL, status code, headers, and response body relevant to HTTP response, separating browser from server failures. Open an isolated test environment and run “curl -I https://example.com”. Write down the expected output first, do not alter production data, and record one safe next diagnostic step.

curl -I https://example.com

Quick check

Can you explain the purpose, observable state, and most common failure source of HTTP response — Web fundamentals in one sentence each? Which evidence would you preserve before changing anything, and which repeated test would prove that the correction actually worked?