---
title: "Comment by -- on \"Stop Wasting Connections, Use HTTP Keep-Alive\" | Hashnode"
description: "from MDN: Connection-specific header fields such as Connection and Keep-Alive are prohibited in HTTP/2 and HTTP/3. Chrome and Firefox ignore them in HTTP/2 resp"
url: "https://hashnode.com/posts/stop-wasting-connections-use-http-keep-alive/636537cbba211b516727dc96/comment/63660b67c7fec996b85c723c"
---

[Discussion](https://hashnode.com/posts/stop-wasting-connections-use-http-keep-alive/636537cbba211b516727dc96)

Comment [Stop Wasting Connections, Use HTTP Keep-Alive](https://hashnode.com/posts/stop-wasting-connections-use-http-keep-alive/636537cbba211b516727dc96)

[\--](https://hashnode.com/@myesolar)

[Nov 5, 2022](https://hashnode.com/posts/stop-wasting-connections-use-http-keep-alive/636537cbba211b516727dc96/comment/63660b67c7fec996b85c723c)

from MDN:

Connection-specific header fields such as Connection and Keep-Alive are prohibited in HTTP/2 and HTTP/3. Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2 specification requirements and does not load any response that contains them.
