[
https://issues.apache.org/jira/browse/WICKET-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030092#comment-16030092
]
ASF subversion and git services commented on WICKET-6385:
---------------------------------------------------------
Commit 4dc6e7eca5cf4849346bbf20b59f1f5d2de6512a in wicket's branch
refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=4dc6e7e ]
WICKET-6385 Allow using custom port for web socket connections
(cherry picked from commit 36c3eb49174596b3a3306059049412c28369c30a)
> Allow using custom port for web socket connections
> --------------------------------------------------
>
> Key: WICKET-6385
> URL: https://issues.apache.org/jira/browse/WICKET-6385
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-native-websocket
> Affects Versions: 8.0.0-M6
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 7.8.0, 8.0.0-M7
>
>
> OpenShift uses custom ports for WS and WSS proxies [1].
> It would be nice if there is a way to specify those ports via
> WebSocketSettings.
> 1. https://blog.openshift.com/paas-websockets/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
