Hi
here is my configuration on vs
stream enable to fix web content mix http to https, asm enable, port vs 443 and pool 80
is that related wss invalid frame header ?
Hi
here is my configuration on vs
stream enable to fix web content mix http to https, asm enable, port vs 443 and pool 80
is that related wss invalid frame header ?
Hello,
Can you post TMOS version and any relevant ASM event logs when a WSS is made? Can you provide more details on your VS configuration as well? Quick search shows ASM/WAF in relation to WebSocket.. The BIG-IP ASM system fails to detect WebSocket URLs. Also you might want to review this other community article which might address this issue:BIG-IP WAF Causes WSS Connections to Stall | DevCentral
Hello
os version 17.5.1 asm template rapid deployment and Differentiate between HTTP/WS and HTTPS/WSS URLs is enable
config on vs
stream enable to replace http to https port vs https and pool http
Do you have a websocket profile enabled on this VS? If not please add one and re-test
no websocket profile on virtual server
should i add to client and server too ? because when i applied on client error indicate that i have to add on server to ?
is that possible when pool member is htp (plaintext) o
Its worth a try. Are you able to post the actual error message ?
It is usually a missing websocket profile.