[asterisk-bugs] [JIRA] (ASTERISK-26891) Re-enable plain WebSockets in pjsip for reverse proxies

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242382#comment-242382 ] 

Asterisk Team commented on ASTERISK-26891:
------------------------------------------

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

> Re-enable plain WebSockets in pjsip for reverse proxies
> -------------------------------------------------------
>
>                 Key: ASTERISK-26891
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26891
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.15.0
>            Reporter: Ludovic Gasc (Eyepea)
>            Assignee: Unassigned
>
> In this commit, you removed the plain WebSockets support in pjsip:
> https://github.com/asterisk/asterisk/commit/75ebd8f0d2cdd146ab071391334ec7106ff29e94
> Your justification in your commit is: "Firefox and Chrome do not support anything other than secure websockets anymore."
> It's true, however, at least to us, we have a valid use case to have plain WebSocket: To share the same HTTPS port with our APIs, we have a HAProxy to handle TLS, take care about crappy TCP connections, and depends on the URL, redirect the HTTP request to the right server.
> We keep the internal traffic in HTTP instead of HTTPS to reduce the CPU usage, and mainly to capture easily for debugging purposes.
> To my knowledge, at least Kazoo does also like that, and it's a pattern used a lot in the Web world with HAProxy.
> Could you keep unencrypted WebSockets in pjsip ?
> Thank you a lot.



--
This message was sent by Atlassian JIRA
(v6.2#6252)