[asterisk-bugs] [JIRA] (ASTERISK-21279) Allow WebSocket connections on URL's other than /ws

[David M. Lee (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David M. Lee reassigned ASTERISK-21279:
---------------------------------------

    Assignee: David M. Lee
    
> Allow WebSocket connections on URL's other than /ws
> ---------------------------------------------------
>
>                 Key: ASTERISK-21279
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21279
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/Stasis, Resources/res_stasis_http
>            Reporter: David M. Lee
>            Assignee: David M. Lee
>              Labels: Asterisk12
>
> The current WebSocket support uses the WebSocket subprotocol for connection routing, and all requests funnel to the {{/ws}} URL.
> This could be problematic for deploying Asterisk for use with WebRTC, since both WebRTC and Stasis-HTTP use WebSockets. This potentially exposes the Stasis-HTTP API's to the outside world, which would certainly give me the willies about deploying it.
> The Stasis WebSocket should listen on a different URL, such as {{http://localhost:8088/stasis/api/events}}. (WebRTC can keep {{/ws}}, since it was there first.) An HTTP proxy in front of Asterisk can forward only {{/ws}} requests, leaving Stasis-HTTP on the trusted side of the firewall.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira