Connection general header controls whether or not the
network connection stays open after the current transaction finishes. If the value sent
keep-alive, the connection is persistent and not closed, allowing for
subsequent requests to the same server to be done.
Connection-specific header fields such as
Keep-Alive are prohibited in HTTP/2.
Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2
spec requirements and won’t load any response which contains them.
Except for the standard hop-by-hop headers (
hop-by-hop headers used by the message must be listed in the
header, so that the first proxy knows it has to consume them and not forward them
further. Standard hop-by-hop headers are also required to be listed.
|Header type||Request header, Response header|
|Forbidden header name||yes|
Connection: keep-alive Connection: close
- Indicates that either the client or the server would like to close the connection. This is the default on HTTP/1.0 requests.
- any comma-separated list of HTTP headers [Usually
- Indicates that the client would like to keep the connection open. Having a persistent connection is the default on HTTP/1.1 requests. The list of headers are the name of the header to be removed by the first non-transparent proxy or cache in-between: these headers define the connection between the emitter and the first entity, not the destination node.
BCD tables only load in the browser