[
https://issues.apache.org/jira/browse/WAVE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vicente J. Ruiz Jurado resolved WAVE-357.
-----------------------------------------
Resolution: Fixed
Fixed with: https://reviews.apache.org/r/5375/
> Websocket configurable in a different port and/or subdomain
> ------------------------------------------------------------
>
> Key: WAVE-357
> URL: https://issues.apache.org/jira/browse/WAVE-357
> Project: Wave
> Issue Type: Improvement
> Reporter: Vicente J. Ruiz Jurado
> Assignee: Vicente J. Ruiz Jurado
> Attachments: websocket-subdomain.patch
>
>
> The idea is that the client uses two configurable listening addresses:
> - one for the normal traffic (all the common server petitions), the current
> http_frontend_public_address
> - and a new one for the websocket traffic (that can be configured to a
> different subdomain or port if it's necessary).
> That is, we would be able to split these two different traffics. This would
> allow the use of proxies, caches or CDNs for the "normal traffic".
> I'll attach a patch for review.
--
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
