[
https://issues.apache.org/jira/browse/WAVE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446824#comment-13446824
]
Ali Lown commented on WAVE-366:
-------------------------------
Hmm, I have just deployed the current trunk (includes your configurable
websockets patch) and since the SSL certificate correctly matches the HTTPS and
WSS domains, there are no issues with using SSL there.
My local test ssl setup uses the same certificate + key (so CA signed, but
incorrect domain), Chrome complains but lets me continue to the website, but
the websockets are intermittent (as documented above).
It is most interesting, that this wasn't ever a problem until your patch was
pushed, but I suppose it only used to work because I relied on undefined
behaviour...
> Websockets fail to connect to server with SSL enabled
> -----------------------------------------------------
>
> Key: WAVE-366
> URL: https://issues.apache.org/jira/browse/WAVE-366
> Project: Wave
> Issue Type: Bug
> Components: Server
> Reporter: Ali Lown
> Assignee: Ali Lown
> Labels: ssl, websocket
>
> I think it is a result of review #5375 for WAVE-357.
> Disabling SSL allows the websocket to connect to the configured port without
> issue.
> When SSL is enabled, although wss is correctly used, the socket is unable to
> be established.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
