PROTOCOL EXPLORERLearn how the internet works
Now learningHTTP · Web communicationOverview · 5 steps
Learning progress0%
0 / 14 complete · 0 in progress
Client192.168.1.10Router192.168.1.1InternetDNS Resolver8.8.8.8Web Server203.0.113.10

Protocol overview

HTTP

Active

Hypertext Transfer Protocol

HTTP defines the messages exchanged by a browser and a web server. A client requests a resource, and the server returns a status, headers and often a body. In HTTP/1.1 the start line and headers are readable text; the body can carry HTML, images or other media.

Layer
Application (Layer 7)
Default port
80 (HTTPS: 443)
Transport
TCP
Data format
Text · headers + optional body
Common methods
GET, POST, PUT, DELETE, HEAD
Defined in
RFC 9110, RFC 9112
Read the complete guide ↗

Packet flow

DNSTCPRequestResponse
No.TimeSourceDestinationProtocolInfoSize
10.000s192.168.1.108.8.8.8DNSStandard query A www.example.com75 B
20.012s8.8.8.8192.168.1.10DNSStandard query response A 203.0.113.1091 B
30.024s192.168.1.10203.0.113.10TCP52344 → 80 [SYN] Seq=066 B
40.041s203.0.113.10192.168.1.10TCP80 → 52344 [SYN, ACK] Seq=0 Ack=166 B
50.058s192.168.1.10203.0.113.10TCP52344 → 80 [ACK] Seq=1 Ack=160 B
60.058s192.168.1.10203.0.113.10HTTPGET / HTTP/1.1114 B
70.076s203.0.113.10192.168.1.10HTTPHTTP/1.1 200 OK (text/html)132 B

How HTTP Works: Requests and Responses

Trace an HTTP/1.1 GET request and 200 OK response. Inspect the request line, headers and HTML body in an interactive packet lab.

Understanding HTTP

HTTP defines the messages exchanged by a browser and a web server. A client requests a resource, and the server returns a status, headers and often a body. In HTTP/1.1 the start line and headers are readable text; the body can carry HTML, images or other media.

Default port
80
Transport / carrier
TCP (HTTP/1.1 & HTTP/2)
Category
application

What to look for in the lab

Open the GET packet, then the 200 OK response. In the response, find the blank line that separates the headers from the HTML. Compare Content-Length with the bytes after that line.

1. Prepare a request

The browser separates the scheme, hostname and path. A URL fragment stays in the browser and is not sent in the request target.

2. Resolve the hostname

DNS maps the name to an address. A cached answer can avoid a network lookup until its TTL expires.

3. Open the connection

TCP exchanges SYN, SYN-ACK and ACK before the HTTP/1.1 request. Sequence numbers track byte positions, not packet counts.

4. Exchange representations

GET / asks for a resource. A 200 response carries a representation; Content-Length counts body bytes, while Content-Type describes the media type.

5. Render and reuse

The browser parses HTML and may request CSS, scripts and images. Persistent connections can serve later requests without another handshake.

Protocol relationships

Protocols cooperate across layers. Compare the neighboring lessons to distinguish addressing, delivery, application semantics and encryption.

Standards and editorial method

Written and implemented independently by NavSprout. Lessons summarize public protocol standards using synthetic documentation addresses and fictional credentials. Consult the standards for complete wire formats and normative behavior.

RFC 9110 ↗ RFC 9112 ↗

Check your understanding

What does a 404 response mean?