[
https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-19850:
---------------------------------------
After long conversation on #jetty, with [~maxandersen], and andy. This can only be
accomplished by modifying the bootclasspath in order to handle the TLS negotiation to
upgrade to SPDY. If there were a way to take an existing connection and convert it to
SPDY, the TLS negotion would not be necessary and there would be no need to modify the
bootclasspath. Only trying jetty, this is not currently possible. Additionally, it
requires us to use an old jetty version. [~maxandersen] is to contact the jetty team about
possibly fixing up jetty to support our usecase. Given our current deadlines, we are
punting for now, requiring the user to install openshift cli, shell out the portforwarding
logic.
As a user I want to easily set up port forwarding for my application
--------------------------------------------------------------------
Key: JBIDE-19850
URL:
https://issues.jboss.org/browse/JBIDE-19850
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Andre Dietisheim
Priority: Blocker
Labels: openshift_v3, port_forwarding_wizard
Fix For: 4.3.0.Beta2
As a user I want to be able to easily set up port forwarding to my application
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)