Web request-response protocol, secured with TLS.
HTTP is the request-response protocol of the web: methods, headers, status codes, cookies and caching. HTTPS wraps HTTP in TLS providing encryption, integrity and server authentication with certificates. HTTP/2 multiplexes streams; HTTP/3 uses QUIC.
The browser's padlock indicates a verified HTTPS connection.
HTTP and HTTPS carry nearly all web traffic, so understanding requests and responses explains how web applications work.
Web request-response protocol, secured with TLS.
HTTP and HTTPS carry nearly all web traffic, so understanding requests and responses explains how web applications work.
HTTPS wraps HTTP in TLS encryption, which protects data in transit and lets the client verify the server's identity.
Storing state, such as a session identifier, between requests, which HTTP itself does not keep.
Typical applications include sending a form from a browser to a server and reading the response, debugging an API call that returns an error code and securing a login page with HTTPS so passwords are not sent in clear text.
Study "DNS" first (topic 69 of 104 in Software & Computing). It covers the groundwork this topic builds on.
Status 200, 301, 404, 500. TLS handshake. Certificate authorities.
The browser's padlock indicates a verified HTTPS connection.
The next topic is "Network security basics", which builds directly on this one.
It is classed as Intermediate in Software & Computing (topic 70 of 104). It is an intermediate topic. Work through the beginner topics in Software & Computing first.
Want to practise? Open the interactive course for quick checks, quizzes, simulations and progress tracking.