[ https://issues.jboss.org/browse/ISPN-6676?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6676: ------------------------------------------- Thoughts on design for this feature: * HTTP/2 [does not support upgrading to another protocol|https://http2.github.io/http2-spec/#rfc.section.8.1.2.2]. [TLS ALPN|https://http2.github.io/http2-spec/#rfc.section.3.1] should be used to ensure this type functionality. * HTTP/1.1 Upgrade header is supported to ensure backwards compatibility. In other words we should consider using [HTTP/1.1 Upgrade|https://http2.github.io/http2-spec/#rfc.section.3.2] or [ALPN|https://tools.ietf.org/html/rfc7301] to support this kind of functionality. * [HTTP/2 client with TLS support must use ALPN|https://http2.github.io/http2-spec/#rfc.section.3.4] * [HTTP/2 supports extensions, which can use new type of Frames, Settings and Error Codes|https://http2.github.io/http2-spec/#rfc.section.5.5]. * HTTP/2 supports [PING|https://http2.github.io/http2-spec/#rfc.section.6.7] and [CLOSE|https://http2.github.io/http2-spec/#rfc.section.6.8] operations out of the box. * [ALPN is considered as a protection for cross-protocol attacks|https://http2.github.io/http2-spec/#rfc.section.10.2] for HTTP/2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)