Ok will take a look. But router timeouts shouldn’t impact web socket connection as it should be under tunnel type mode.
Will play aroud it. It would be nice if we have a documenaiton to cover it …
"ccoleman redhat com" <ccoleman redhat com>
Date: Tuesday, December 6, 2016 at 3:55 PM
To: Srinivas Naga Kotaru <skotaru cisco com>
Cc: dev <dev lists openshift redhat com>
Subject: Re: web socket support
You would just listen on whatever port is exposed by the route (the target port). You can create multiple routes if necessary. Router allows Connection: Upgrade headers seamlessly. Connection timeouts on the router matter, of course.
The router documentation briefly describes it, mostly because it just works.
On Dec 6, 2016, at 6:51 PM, Srinivas Naga Kotaru (skotaru) <skotaru cisco com> wrote:
Can you point me any documentation to see how it works or implemented?
It's fully supported and has been since 3.0
On Tue, Dec 6, 2016 at 5:55 PM, Srinivas Naga Kotaru (skotaru) <skotaru cisco com> wrote:
What is OpenShift strategy or plans to support web socket support at router layer? Our clients asking web socket support since Openshift 2 days onwards.
I knew Openshift 2 has limited apache based node proxy but that is not a full web socket support.
Would like to hear from your for OpenShift 3
dev mailing list
dev lists openshift redhat com