Altostratusif you do not offload (or bridge - decrypt / re encrypt) SSL on the BIG-IP you can't do other profiles as the BIG-IP can only the encrypted traffic, which it can't read / understand.
Hi,
So websockets is part of the html payload.
So you need to be able to see that payload for the profile to take affect.
Have you got the client ssl and server ssl configuations on?
Before you enabled the websockets profile, was this a working setup?
AltostratusWe did not off-load ssl in our LTM (Local Traffic Manager, i4800; BIG-IP 16.1.0 Build 0.0.19 Final). We only create sessions for 443 https virtual servers, ssl is maintained by internal servers. So, this was a working setup.
Now the application vendor needs the WebSocket session. I just enable it in the virtual server as follows, and then the total communication stops.
to do this, we need to enable http profile
it seems I am not on the right track.
