HTTP

HTTP stands for Hypertext Transfer Protocol, the application-layer protocol used to transfer data between clients and servers on the web.

It defines how browsers, APIs, applications, and servers format requests and responses when exchanging resources such as HTML pages, JSON data, images, files, and other content.

Also known as: Hypertext Transfer Protocol.

How Does HTTP Work?

HTTP follows a request-response model.

A typical interaction looks like this:

1. A client sends an HTTP request.
2. The request specifies a method, target resource, headers, and optionally a body.
3. The server processes the request.
4. The server returns an HTTP response.
5. The response includes a status code, headers, and optionally a body.
6. The client processes the returned content.

A simplified flow looks like:

Client
  ↓
HTTP Request
  ↓
Server
  ↓
HTTP Response
  ↓
Client

HTTP Request

An HTTP request is a message sent by a client to a server.

A request may contain:

• Request method
• Path
• HTTP version
• Headers
• Query parameters
• Cookies
• Request body

For example:

GET /products HTTP/1.1
Host: example.com
Accept: application/json

This request asks the server for the /products resource.

HTTP Response

An HTTP response is the message returned by the server.

It may contain:

• HTTP version
• Status code
• Response headers
• Response body

For example:

HTTP/1.1 200 OK
Content-Type: application/json

The response body may then contain structured data such as:

{
  "product": "Wireless Mouse",
  "price": 29.99
}

Common HTTP Methods

HTTP methods describe the action a client wants to perform.

GET

GET retrieves a resource.

Typical uses include:

Load a webpage
Retrieve API data
Download a file

POST

POST sends data to the server.

It is commonly used for:

Submitting forms
Creating records
Sending API requests

PUT

PUT is commonly used to replace or update an existing resource.

PATCH

PATCH is typically used to make a partial update to a resource.

DELETE

DELETE requests removal of a resource.

HEAD

HEAD requests response headers without the full response body.

OPTIONS

OPTIONS asks the server which communication methods or options are supported.

HTTP Status Codes

HTTP status codes indicate the result of a request.

They are grouped into several categories.

1xx: Informational

These codes indicate that a request has been received and processing is continuing.

2xx: Success

These indicate successful requests.

Common examples include:

200 OK
201 Created
204 No Content

3xx: Redirection

These tell the client that additional action may be required.

Common examples include:

301 Moved Permanently
302 Found
304 Not Modified

4xx: Client Errors

These indicate a problem with the request.

Common examples include:

400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
429 Too Many Requests

5xx: Server Errors

These indicate that the server failed to complete a valid request.

Common examples include:

500 Internal Server Error
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout

HTTP Headers

HTTP headers provide metadata about requests and responses.

Common request headers include:

Host
User-Agent
Accept
Authorization
Cookie
Content-Type

Common response headers include:

Content-Type
Content-Length
Cache-Control
Set-Cookie
Server
Location

Headers can control authentication, caching, content negotiation, cookies, and other behaviors.

HTTP Request Body

Some HTTP methods can include a request body.

For example, a client may send JSON data:

{
  "name": "Wireless Mouse",
  "price": 29.99
}

The Content-Type header can indicate the data format:

Content-Type: application/json

HTTP vs. HTTPS

HTTP and HTTPS use the same general request-response model, but HTTPS adds encryption through TLS.

In simple terms:

• HTTP: Transfers web traffic without transport-layer encryption.
• HTTPS: Encrypts the connection between client and server.

HTTPS helps protect information such as:

• Passwords
• Authentication tokens
• Payment details
• Personal information
• Session cookies

Modern websites commonly use HTTPS rather than unencrypted HTTP.

HTTP vs. TCP

HTTP and TCP operate at different layers.

HTTP defines how web requests and responses are structured.

TCP provides reliable transport between systems.

In simple terms:

• HTTP: Defines web communication messages.
• TCP: Handles reliable delivery of network data.

Traditional HTTP versions commonly operate over TCP.

HTTP Versions

HTTP has evolved through several versions.

HTTP/1.1

HTTP/1.1 introduced persistent connections and remains widely supported.

HTTP/2

HTTP/2 improved efficiency through features such as:

• Multiplexing
• Header compression
• Binary framing

Multiple requests can share a single connection more effectively.

HTTP/3

HTTP/3 uses QUIC instead of traditional TCP transport.

It is designed to reduce connection latency and improve performance under changing network conditions.

HTTP and APIs

HTTP is the foundation of many web APIs.

An application may use methods such as:

GET    Retrieve records
POST   Create records
PATCH  Update records
DELETE Remove records

API responses commonly use structured formats such as JSON.

For example:

{
  "id": 1001,
  "name": "Wireless Mouse",
  "available": true
}

HTTP and Proxies

HTTP traffic can be routed through a proxy server.

A simplified connection may look like:

Client
  ↓
HTTP Proxy
  ↓
Destination Server

The proxy receives the client's request and forwards it to the destination.

Depending on the proxy configuration, it may:

• Forward requests
• Add or modify headers
• Apply authentication
• Cache responses
• Filter traffic
• Route requests through another IP address

HTTP and Web Data Collection

HTTP is fundamental to web scraping and API-based data collection.

A typical workflow may look like:

Send HTTP Request
       ↓
Receive HTTP Response
       ↓
Check Status Code
       ↓
Parse Response
       ↓
Extract Required Data
       ↓
Store Results

For server-rendered pages, the required data may be available directly in the HTTP response.

For JavaScript-heavy applications, additional browser rendering may be needed after the initial HTTP request.

HTTP Error Handling

Automated systems should interpret HTTP status codes before processing a response.

For example:

200 → Process response
404 → Resource not found
429 → Request rate exceeded
500 → Server error

Different errors may require different responses, such as retrying later, skipping the resource, or recording the failure for analysis.

Example

Suppose a client requests product information.

The request may look like:

GET /products/1001 HTTP/1.1
Host: example.com
Accept: application/json

The server may return:

HTTP/1.1 200 OK
Content-Type: application/json

with the following body:

{
  "id": 1001,
  "name": "Wireless Mouse",
  "price": 29.99,
  "currency": "USD"
}

The client can then parse the response and use the product information in an application or data pipeline.

Key Takeaway

HTTP, or Hypertext Transfer Protocol, is the core application-layer protocol used for communication between web clients and servers.

It defines how requests and responses are structured through methods, headers, status codes, and message bodies. HTTP powers webpages, APIs, proxies, and many web data workflows, while HTTPS adds encryption to protect data in transit.