HTTP stands for Hypertext Transfer Protocol. It defines how clients ask for resources and how servers respond. HTTPS uses HTTP over a connection protected by TLS, helping protect data in transit and authenticate the server for the requested name.
Follow one exchange
Opening a web page usually starts a sequence of requests: the document, then resources such as style sheets, images, and scripts. A browser acts as a client; servers and intermediaries such as caches participate in delivering responses. The shared meaning of methods, fields, and statuses is defined by HTTP Semantics.
This abbreviated, fictional HTTP/1.1 exchange asks for an HTML guide. A blank line separates headers from a body. Headers describing message framing are omitted for teaching:
GET /guide.html HTTP/1.1
Host: example.org
Accept: text/html
--- illustrative server response ---
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
<!doctype html>
<title>A short guide</title>
<p>Hello from the guide.</p>GET asks for a representation of the resource. The response status is 200; Content-Type identifies the returned format. Accept describes formats the client can accept. HTTP/2 and HTTP/3 encode exchanges differently while retaining these core meanings; the text above is a teaching view of HTTP/1.1.
Interpret a status code
| Status | Meaning | Next check |
|---|---|---|
| 200 OK | The request succeeded. | Read the actual content; a success status alone does not establish that an application returned the result you wanted. |
| 301 / 308 | Permanent redirect. | Inspect the Location destination. 308 preserves the request method; 301 can lead a POST to be retried as GET. |
| 304 Not Modified | A conditional request can use a stored representation. | Check caching and validation; this is a response without the resource body. |
| 401 / 403 | 401 requests authentication; 403 refuses the request. | Check the intended login and access permissions. |
| 404 Not Found | The server has no current representation to provide for that target, or will not disclose one. | Check spelling, path, and the site’s navigation. |
| 500 / 503 | An internal error or temporary inability to serve the request. | Record the URL and time; check service status and retry guidance. |
A status belongs to one request. A page can return 200 while an image returns 404. Browser connection failures, DNS errors, and certificate errors may occur before any HTTP response exists. Use the IANA HTTP status-code registry to look up an unfamiliar code.
Inspect a request in the browser
- Open a public page you recognize, then open the browser's developer tools and choose Network.
- Reload the page with that panel open. Select the main document request; then try an image or stylesheet request.
- Read the request URL, method, status, and response Content-Type. A redirect may appear as a separate request followed by another destination.
- Compare the Response or Preview pane with the resource you expected. Use Timing to distinguish stages of the request.
The Chrome Network tutorial shows these controls. Labels vary by browser. Cached resources can have different transfer behavior on a second load; record whether you disabled cache if you are comparing runs.
Worked diagnosis: a missing illustration has a 404 request for /images/chart.jpg, while the HTML document succeeds. First verify the image path and deployed filename, including capitalization. Rewriting the page's prose or changing its MIME label would not create the missing file.
Read headers in context
Content-Type identifies the representation's media type. Content-Encoding describes an additional coding such as compression. Cache-Control supplies cache directives. Location commonly provides a redirect destination. See MIME and media types for how file formats are identified.
Applications can maintain sessions with cookies even though HTTP requests have independently defined semantics. Developer-tool exports may include cookies, authorization fields, query tokens, or personal data. Remove those before sharing a diagnostic capture.
HTTPS protects communication on the connection; a deceptive site can also obtain a certificate for its own name. Check the URL's host and the site's identity. If the browser displays a certificate warning, resolve the name, clock, or certificate problem through the responsible operator rather than bypassing it.
For further protocol detail, HTTP/1.1, HTTP/2, and HTTP/3 specify their respective message and transport arrangements. Begin troubleshooting with the specific request and response before changing protocol settings.