[
https://issues.apache.org/jira/browse/WICKET-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030133#comment-16030133
]
ASF subversion and git services commented on WICKET-6385:
---------------------------------------------------------
Commit d18ae6938fc85d85b072dd8f6e3794eae84fd568 in wicket's branch
refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=d18ae69 ]
WICKET-6385 Allow using custom port for web socket connections
Fix the build after cherry-pick
> 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)
