Draft: Fix/rapid cdn assure http1.1 websocket client origin
When websocket is used it shall be assured that CDN will only use HTTP/1.1 from the client and to the backend, otherwise this will lead to problems. The CDN shall assure such scenario, even if the cluster or slave is using other protocol versions (especially HTTP/2 or HTTP/3).
Tasks:
-
make the backend accepting HTTP/2 connections too (if it is SSL one) -
assure that by default HTTP/2 is used to backend connection by default -
assure that if slave is type:websocket, then connectivity to backend is like this - or if incoming connection is websocket style?