HTTP/1.0 Persistent Connections: Difference between revisions
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
HTTP/1.0 clients can request a persistent connection by using "Connection: Keep-Alive" header. Early versions of the HTTP/1.1 specification also describe this mechanism. | |||
It is the client that initially requests the connection to be kept alive. The persistent connection is initiated by specifying a "Keep-Alive" value for the "Connection" request header: | It is the client that initially requests the connection to be kept alive. The persistent connection is initiated by specifying a "Keep-Alive" value for the "Connection" request header: | ||
Revision as of 05:37, 8 January 2017
Internal
Overview
HTTP/1.0 clients can request a persistent connection by using "Connection: Keep-Alive" header. Early versions of the HTTP/1.1 specification also describe this mechanism.
It is the client that initially requests the connection to be kept alive. The persistent connection is initiated by specifying a "Keep-Alive" value for the "Connection" request header:
GET ... HTTP/1.0 Host: ... Connection: Keep-Alive
The server may or may not support persistent connections. If the server does support them, it will confirm that by including with the response a "Connection" response header:
200 OK Content-Length: ... Connection: Keep-Alive
Once both the client and the server have agreed on using persistent connections, they will keep the underlying TCP/IP connection open, and subsequent requests from that client will be sent over the persistent connection.