Developers often say that a browser sent a request, but several exchanges may occur first: a DNS query, a transport connection, a TLS handshake, and finally one or more HTTP requests. In web development, request usually means the HTTP message sent to an application.
Different Kinds of Network Requests
DNS query -> TCP or QUIC setup -> TLS handshake -> HTTP request -> HTTP response
What an HTTP Request Contains
An HTTP request identifies a method and target, then supplies metadata in headers and, when needed, data in a body. The wire format differs between HTTP versions, but these conceptual parts remain useful.
Request example
POST /users?sendWelcome=true HTTP/1.1Host: api.example.comAuthorization: Bearer <token>Content-Type: application/json{ "name": "Nikhil", "email": "nikhil@example.com" }- Method
- Describes the intended action, such as GET or POST.
- Path
- Identifies an application route or resource, such as /users.
- Headers
- Carry metadata such as content type, cookies, credentials, and accepted formats.
- Body
- Carries submitted data when the request needs a payload.
Common HTTP Methods
- GET
- Retrieve a representation, for example GET /products/100.
- POST
- Submit data or create something, for example POST /users.
- PUT
- Replace the current representation of a resource.
- PATCH
- Apply a partial update rather than replacing everything.
- DELETE
- Ask the server to remove a resource.
- HEAD
- Request headers similar to GET without a response body.
- OPTIONS
- Discover communication options; browsers also use it for CORS preflight.
HTTP Request Methods
Methods communicate intent, but the application still decides what a route does. HTTP semantics are a contract used by clients, caches, proxies, and developers—not an automatic security boundary.
How to Read a URL
Understanding URL Components
URL anatomy
https://api.example.com:443/products/100?currency=INR#detailsscheme: https | hostname: api.example.com | port: 443path: /products/100 | query: currency=INR | fragment: detailsThe hostname is resolved to an address, the port selects the service, and the path and query are sent to the server. The fragment is normally interpreted only by the browser and is not included in the HTTP request.
Headers and Bodies Have Different Jobs
Content-Type describes the body; Accept describes response formats the client can handle; Authorization or cookies may carry credentials. The body contains data such as JSON, form fields, or uploaded bytes. A GET can have query parameters without a body, while a POST can carry a body without a query string.
Remember
HTTP describes an application conversation. It still needs DNS to find the host, transport to carry bytes, and usually TLS to protect them.
Series
How Internet Requests Actually WorkAn eight-part beginner series tracing internet communication from an HTTP request through DNS, IP, ports, transport protocols, packets, network devices, server infrastructure, security, and troubleshooting.
HTTP Requests: Methods, URLs, Headers, and Bodies
Start at the application layer and understand what a browser or API client is actually asking for.
DNS, Domain Names, and IP Addresses
Follow the lookup that turns a human-friendly hostname into a network destination.
Public IP, Private IP, NAT, and Ports
See how local devices reach the internet and how operating systems identify each service and flow.
TCP vs UDP
Compare reliable byte streams with simpler datagrams and understand where each transport fits.
Packets, Network Layers, Switches, and Routers
Learn how data is encapsulated and moved across local links and routed networks.
The Complete Website Request Journey
Put the layers together from the browser to production infrastructure and back again.
HTTPS, TLS, and HTTP Status Codes
Understand secure transport, certificate checks, and the response codes used during debugging.
Troubleshooting, Localhost, Cloud, and Containers
Apply the model with diagnostic tools and carry it into cloud and container environments.
Nikhlesh Yadav is a Technical Lead and Solution Architect with 12+ years of experience across cloud-native systems, distributed platforms, AI integrations, Web3, and cyber security.
Read full profile