🎁 New User? Get 20% off your first purchase with code NEWUSER20 · ⚡ Instant download · 🔒 Secure checkout Register Now →
Menu

Categories

Networking Beginner

What is HTTP Keep-Alive?

An HTTP mechanism that reuses a single TCP connection for multiple requests, reducing the overhead of establishing new connections.

HTTP Keep-Alive (persistent connections) allows multiple HTTP requests and responses to share a single TCP connection, eliminating the overhead of TCP handshakes and TLS negotiations for each request. In HTTP/1.1, connections are keep-alive by default (Connection: keep-alive header). Servers configure maximum requests per connection and idle timeout. Keep-alive significantly improves page load times for sites with many resources (images, CSS, JS files) — each resource does not require a new connection. HTTP/2 extends this further with multiplexing (multiple concurrent requests on one connection). Web servers like Nginx configure keepalive_timeout and keepalive_requests directives.

Related Terms

WireGuard
A modern, lightweight VPN protocol that uses state-of-the-art cryptography and minimal code for fast, secure tunneling.
Reverse Proxy
A server that sits between clients and backend servers, forwarding client requests and returning server responses on their behalf.
Overlay Network
A virtual network built on top of an existing physical network, enabling features like container networking and VPNs.
QoS (Quality of Service)
A set of techniques for managing network traffic to prioritize certain types of data and ensure performance for critical applications.
SNMP (Simple Network Management Protocol)
A protocol for monitoring and managing network devices like routers, switches, servers, and printers remotely.
VLAN (Virtual LAN)
A logical grouping of network devices that creates separate broadcast domains on the same physical network infrastructure.
 View All Networking Terms →