3 ms·
That's funny, we couldn't deploy H2 because there were problems with HAProxy/Apache and Safari. And it looks like a very similar issue: http://www.wiktorzychla
by kolme 9y ago
That's funny, we couldn't deploy H2 because there were problems with HAProxy/Apache and Safari. And it looks like a very similar issue:
http://www.wiktorzychla.com/2017/06/http2-keep-alive-and-safari-browsers.html http://www.wiktorzychla.com/2017/06/http2-keep-alive-and-saf...
- ghusbands 9y agoThat bug is in HAProxy. The RFC clearly states that the presence of the Connection header makes the response malformed. "An endpoint MUST NOT generate an HTTP/2 message containing connection-specific header fields; any message containing connection-specific header fields MUST be treated as malformed (Section 8.1.2.6)." and "Clients MUST NOT accept a malformed response. Note that these requirements are intended to protect against several types of common attacks against HTTP [...]" (though Safari's response of repeatedly retrying as fast as possible is certainly problematic)