Websockets for https backends


#1

Websocket end points that are on SSL ( https://target ) seems to dial the backend on port 80 - probably due to function canonicalAddr()

to overcome that, the target endpoints are made like https://target:443/ and it seems to work

Please validate.


#2

Yes you must specify the target as Https if you want to have websockets work - Tyk needs to decrypt the inbound and re-encrypt the outbound for the copy operations to work, Tyk does not just pass through the socket.


#3

Hi Martin
I meant to say that when the target is on default SSL port, then on the target url for the API “:443” has to be explicitly specified. I am not sure if this is expected behavior. If so, it can be documented. Please clarify.


#4

We will update the docs to clarify.