App service engineering team has identified that this issue happened after recent upgrade. This happens if the http response 101 Switching Protocol has the Content-Length header.
Please check if you can remove the Content-Length response header in your application to mitigate this issue as we have seen successful behavior after removing this header.
This is temporary workaround. Permanent fix will be rolled out soon and it may take 1-2 weeks