HTTP defines the messages a browser and server exchange. HTTPS sends those same messages through TLS, a protocol that protects the connection and helps the browser verify the server.
Web Security · Lesson 2
HTTPS
Learn to identify the part of a web request protected by HTTPS.
Identifying the Protected Connection
Imagine a browser connecting to https://site.example. After setting up TLS, the browser and server can exchange encrypted HTTP messages. Someone observing that part of the network cannot simply read the HTTP body or change it undetected.
Browser ===== HTTPS connection ===== Website server
The web browser must still validate the identity the server presents.
What does HTTPS protect in this simple setup?
Reading a Multi-Hop Path
A proxy can receive a browser's request and forward it to a separate server. If the proxy ends TLS, it can read the request before passing it along. The next connection needs its own protection. Evaluating each connection matters.
Browser === HTTPS === Proxy --- HTTP --- Internal server
In this diagram the outer connection uses TLS. The inner connection is plain HTTP.
Which hop needs a separate change to gain TLS protection?
Keeping Access Decisions Separate
A valid secure connection helps you trust the server identity and protects messages in transit. The application still decides which account can read a page or change a setting. A private page can have strong TLS and still require an application access policy.
What should the service check before returning a private account page?
Lesson complete
You finished HTTPS
You can now describe what HTTPS protects along a web request's path.
Identify where TLS starts and ends.
Check each hop when a proxy forwards the request.
Recognize why the application still needs access controls.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account