LTM/ASM 11.5.4 websocket

Found a solution. Using a local traffic policy that disables the asm and forwards to the pool if traffic with a http-header named upgrade contains websocket did the trick. This is the first rule. Second rule enables the asm policy and forwards to the pool, last is the default rule which disables the asm

Hey, I also have issues with websockets which were described in the thread below:

https://devcentral.f5.com/questions/issues-with-reverse-proxying-the-application-using-socketio-and-secure-websockets-52213?tag=application%20delivery

Did You do anything specific to enable websocket support ? Thanks a lot

No , without the modification websocket traffic was not going through and the application had a fallback for this case. After applying the solution as described above the websocket was able to open and stay connected. If you like more information about the actual local traffic policy let me know.