What is HTTP Keep-Alive?
A persistent connection feature that reuses TCP connections across multiple HTTP requests.
Definition
HTTP Keep-Alive (also called persistent connections) allows multiple HTTP requests and responses to be sent over a single TCP connection instead of opening a new connection for each request. This reduces latency by eliminating the TCP handshake and TLS negotiation overhead for subsequent requests. Keep-Alive is the default behavior in HTTP/1.1 and is managed through the Connection header and timeout settings.
Simple Analogy
Like keeping a phone line open between calls instead of hanging up and redialing each time — the connection is already established, so subsequent conversations start faster.
Why It Matters
For cron jobs that make frequent HTTP requests (e.g., every minute), connection reuse significantly reduces latency and server load. Without Keep-Alive, each execution pays the full cost of TCP and TLS handshake, which can add hundreds of milliseconds. CronJobPro uses persistent connections to minimize request overhead and improve execution speed.
How to Verify
Check your server response headers for "Connection: keep-alive" and "Keep-Alive: timeout=N". Use curl with verbose mode: "curl -v https://your-endpoint.com" and look for "Connection: keep-alive" in both request and response headers. Monitor your server connection metrics to verify connections are being reused.
Common Mistakes
Setting Keep-Alive timeouts too short (connections close before reuse) or too long (idle connections consume server resources). Not configuring connection pool limits, allowing too many persistent connections. Assuming HTTP/2 and HTTP/3 need Keep-Alive configuration — they handle multiplexing natively.
Best Practices
Enable Keep-Alive on your web server with reasonable timeouts (15-30 seconds for most workloads). Configure connection pool limits based on expected concurrent cron job connections. Monitor idle connection counts to optimize timeout settings. For high-frequency cron jobs, verify that connections are actually being reused through server metrics.
HTTP Methods Guide
Learn about HTTP methods
Try it free →Frequently Asked Questions
What is HTTP Keep-Alive?
HTTP Keep-Alive (also called persistent connections) allows multiple HTTP requests and responses to be sent over a single TCP connection instead of opening a new connection for each request. This reduces latency by eliminating the TCP handshake and TLS negotiation overhead for subsequent requests. Keep-Alive is the default behavior in HTTP/1.1 and is managed through the Connection header and timeout settings.
Why does HTTP Keep-Alive matter for cron jobs?
For cron jobs that make frequent HTTP requests (e.g., every minute), connection reuse significantly reduces latency and server load. Without Keep-Alive, each execution pays the full cost of TCP and TLS handshake, which can add hundreds of milliseconds. CronJobPro uses persistent connections to minimize request overhead and improve execution speed.
What are best practices for HTTP Keep-Alive?
Enable Keep-Alive on your web server with reasonable timeouts (15-30 seconds for most workloads). Configure connection pool limits based on expected concurrent cron job connections. Monitor idle connection counts to optimize timeout settings. For high-frequency cron jobs, verify that connections are actually being reused through server metrics.
Related Terms
Connection Timeout
The maximum time allowed to establish a TCP connection before the attempt is abandoned.
Response Timeout
The maximum time to wait for an HTTP response before considering the request failed.
HTTPS
The secure version of HTTP that encrypts all communication between client and server.
Endpoint
A specific URL where an API or service receives and processes HTTP requests.
Execution Latency
The delay between a job's scheduled time and when it actually begins executing.