Learning term
HTTP status code — Web fundamentals
HTTP status code: A three-digit number classifying success, redirection, or failure of an HTTP response. This card shows its role in “Web fundamentals” and a safe diagnostic path.
Orientation
HTTP status code: A three-digit number classifying success, redirection, or failure of an HTTP response. At this level, separate purpose, input, and visible result. Place HTTP status code within Web fundamentals before changing settings or files.
Practical use
When a web request fails, use `curl -v` to preserve the method, URL, status code, headers, and response body relevant to HTTP status code, separating browser from server failures. Start in a sandbox with neutral examples. Record the expected state, make one controlled change, and compare status output, application behavior, and logs.
Technical understanding
HTTP status code: A three-digit number classifying success, redirection, or failure of an HTTP response. Technically, HTTP status code connects through interfaces, configuration, state, or dependencies. Trace data from input to output and check versions, permissions, networking, storage, and resources separately.
Operations and debugging
When a web request fails, use `curl -v` to preserve the method, URL, status code, headers, and response body relevant to HTTP status code, separating browser from server failures. In production-like operations, use measurable signals, least privilege, reproducible configuration, and a documented rollback. Preserve evidence, isolate the cause, and verify the correction with the same test.
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 status code, 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.comQuick check
Can you explain the purpose, observable state, and most common failure source of HTTP status code — 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?