+ Use
+ Such requests come as a CONNECT with an extra ':protocol' + header. Such requests are transformed inside the module to + their HTTP/1.1 equivalents before passing it to internal + processing. +
+ This means that HTTP/2 WebSockets can be used for a
+
+ For (3rd party) modules that handle WebSockets directly in the + server, the protocol bootstrapping itself will also work. However + the transfer of data does require extra support in case of HTTP/2. + The negotiated WebSocket will not be able to use the client connection + socket for polling IO related events. +
+ Because enabling this feature might break backward compatibility + for such 3rd party modules, it is not enabled by default. +
+