• Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.1 GA, SaaS
    • Gateway

      It would be nice if we support websocket protocal `ws and wss` as a private base URL in the backend.

      We can then modify Apicast to add the policy for https://www.nginx.com/blog/websocket-nginx/. It pretty easy and straightforward.

      *Current behavior:*
      When I try to add the echo ws backend wss://echo.websocket.org it results in error
      `The accepted format is 'protocol://address(:port)'`

      *Expected result:*
      Both http and ws should be supported, as we see more usecases around webscoket API and support using APIcast.

      See also THREESCALE-916

            [THREESCALE-4051] Support websocket backend (gateway)

            Keep it open, 4019 is a epic one.

            Eloy Coto (Inactive) added a comment - Keep it open, 4019 is a epic one.

            All the work has been done in https://issues.redhat.com/browse/THREESCALE-4019. Close this one.

            Eloy Coto (Inactive) added a comment - All the work has been done in https://issues.redhat.com/browse/THREESCALE-4019 . Close this one.

            eloycoto Not sure about the the differences between this issue and THRESCALE-3903. Can they be treated as one single task? Besides, we can link to the PR and set the status to "Ready for QA" right?

            Andreu Masferrer added a comment - eloycoto Not sure about the the differences between this issue and THRESCALE-3903. Can they be treated as one single task? Besides, we can link to the PR and set the status to "Ready for QA" right?

              Unassigned Unassigned
              vbhalera@redhat.com Vinay Bhalerao (Inactive)
              Jakub Smadis Jakub Smadis (Inactive)
              Eloy Coto Eloy Coto (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: