Topic lessonTopic: Networking foundations
HTTP vs HTTPS vs TLS: web requests, protection and errors
HTTP (Hypertext Transfer Protocol) defines requests and responses; TLS (Transport Layer Security) protects a connection and authenticates its peer; HTTPS uses HTTP with that protection. A protected connection does not establish that an application authorizes a user or serves trustworthy content. Follow a page request to identify which layer has actually succeeded.
Distinguish HTTP, HTTPS and TLS, and interpret certificate failures, HTTP status codes and application errors without treating one layer as proof of another.
Understand that DNS can resolve a hostname to an address. This lesson reads synthetic examples; it does not make requests or change certificate settings.
Separate resolution, protection and the application request
- Resolve the name → TLS protectionA resolved address does not establish connectivity or certificate validity.
- TLS protection → HTTP requestSend a request using the protected connection; established connections may be reused.
- HTTP request → HTTP responseRead the status separately from the returned content.
- Resolve the name
- Find destination addresses; cached information may be used.
- TLS protection
- Authenticate the peer and establish confidentiality and integrity.
- HTTP request
- Describe an operation using a method, target and headers.
- HTTP response
- Receive status, headers and, where applicable, content.
Read the URL, method and response separately
| Part | Example | Meaning |
|---|---|---|
| Scheme | https | Use protected HTTP |
| Hostname | www.example.com | Identify the target host |
| Path | /reports/ | Identify the target resource |
| Method | GET | Request a representation of the resource |
| Status | For example, 200 | Describe the response to the request |
HTTP defines request and response semantics. How an application signs users in and who may read a monthly report are additional decisions. Establishing TLS does not mean that the user is signed into the application.
What TLS protects and what certificate checks establish
TLS aims to authenticate peers and protect confidentiality and integrity. A typical web client checks the certificate’s trust chain, validity and correspondence to the requested name. Connection protection is separate from trusting the operator or the information on the page.
The protection boundary depends on deployment. A connection after a TLS-terminating intermediary does not automatically inherit the same protection. This diagram is not evidence of encryption across every hop or in stored data.
Worked example: HTTPS works but a report cannot be read
| Observation | What it establishes | What remains open |
|---|---|---|
| Resolution fails | The name has not resolved through that path | Whether the web application is healthy |
| Certificate validation fails | Peer verification has a problem | Application permissions |
| HTTP 403 | The server refuses to fulfill the request | The refusing layer and its detailed reason |
| HTTP 404 | No current representation is found, or existence is not disclosed | Whether the URL, publication or access design explains it |
| HTTP 200 with an error page | An HTTP success response was received | Whether application processing and content are correct |
Choose an option to see the result and explanation.
Record the layer reached before diagnosing
- Confirm the URL and the operation that reproduces the problem.
- Separate resolution, connectivity, TLS, HTTP and application behavior.
- Record status, visible behavior and time without exposing secrets.
- Do not weaken certificate or access checks on a guess.
- After a correction, test both the intended operation and a relevant denied operation.
Check, then explain in your own words
- Explain HTTP, TLS and HTTPS in one sentence each.
- State what connection protection does and does not establish.
- Compare 403, 404 and an application error returned with 200.
Check your understanding: Does HTTP 200 prove that the content is correct?
No. HTTP status and application correctness require separate checks.
A status code describes the HTTP response semantics. Verify the expected data and application outcome against the application’s own contract and actual response.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
- RFC 9110: HTTP SemanticsChecked:
Scope and conditionsHTTP/HTTPS scheme, methods and response status semantics, including 200, 403 and 404. HTTP status is separate from application correctness.
Used in this lessonSeparate resolution, protection and the application request Read the URL, method and response separately What TLS protects and what certificate checks establish Worked example: HTTPS works but a report cannot be read
Scope and conditionsSection 1 authentication, confidentiality and integrity; connection protection is not an endorsement of content or application authorization.
Used in this lessonSeparate resolution, protection and the application request What TLS protects and what certificate checks establish
- RFC 9499: DNS TerminologyChecked:
Scope and conditionsCurrent BCP terminology; obsoletes RFC 8499 and updates RFC 2308. Resolver, authoritative server, record types and negative answers; not an actual DNS test.
Used in this lessonSeparate resolution, protection and the application request
- RFC 9114: HTTP/3Checked:
Scope and conditionsHTTP semantics mapped to QUIC, with TLS 1.3 at the transport layer; prevents generalizing HTTPS as always a fresh TCP/TLS sequence.
Used in this lessonSeparate resolution, protection and the application request