HTTP, HTTPS & TLS
Describe a web request, response status and what TLS protects.
Requests and responses
HTTP is an application protocol: a client sends a method and target, and the server replies with a status and content. GET retrieves a representation; POST sends data for server-side processing. A 200 status means the request succeeded, 404 means the target resource was not found, and 301 indicates a permanent redirect.
HTTP semantics can run over different transports; HTTP/1.1 commonly uses TCP, while HTTP/3 uses QUIC over UDP.
Where HTTPS fits
HTTPS uses TLS to authenticate the server and protect data in transit between endpoints. The browser checks a certificate for the requested name and a trusted chain. TLS does not mean the website itself is honest or that data stays encrypted after arriving at the server.
A URL's path and request body are ordinarily protected by TLS, while some connection metadata can still be visible to observers.
Check your understanding
Which status most directly indicates a missing requested resource?