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

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26891:
-----------------------------------

    Assignee: Ludovic Gasc (Eyepea)
      Status: Waiting for Feedback  (was: Triage)

The code should allow it to work, we just were not able to test and guarantee it. I'd suggest testing it and if any problems are encountered then providing the information needed to look into it.

> 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: Ludovic Gasc (Eyepea)
>
> 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)