Hide Forgot
> 3. What is the nature and description of the request? State of the art request handling. HTTP/2 is more and more coming for modern web application. OpenShift should be able to handle this native. https://www.eclipse.org/jetty/documentation/current/http2-configuring-haproxy.html > 4. Why does the customer need this? (List the business requirements here) Push message to the browser web application. > 5. How would the customer like to achieve this? (List the functional requirements here) A example solution look like this https://www.eclipse.org/jetty/documentation/current/http2-configuring-haproxy.html > 6. For each functional requirement listed in question 5, specify how Red Hat > and the customer can test to confirm the requirement is successfully implemented. You can use this tool to check if the setup work. https://tools.keycdn.com/http2-test > 7. Is there already an existing RFE upstream or in Red Hat bugzilla? N/A > 8. Does the customer have any specific timeline dependencies? Openshift v 3.x > 9. Is the sales team involved in this request and do they have any additional input? No > 10. List any affected packages or components. openshift3/ose-haproxy-router > 11. Would the customer be able to assis Yes.
If you need more details, just ask here. We will try provide as much as we can here
*** Bug 1425431 has been marked as a duplicate of this bug. ***
This is in 3.11. So the router can accept http/2 connections, but can not use http/2 to the backend because haproxy does not yet have that capability. https://github.com/openshift/origin/pull/19968