Closed vasekd closed 5 years ago
Now Total.js doesn't support fragmentation. I didn't have any problem yet because I still work with messages with the fixed length. Fragmentation is about messages with uknown size. We can look into it but I don't have any idea how to implement it.
It seems that this is the problem of traefik websocket layer
I have found this definition: An intermediary MUST NOT change the fragmentation of a message if any reserved bit values are used and the meaning of these values is not known to the intermediary.
o An intermediary MUST NOT change the fragmentation of any message in the context of a connection where extensions have been negotiated and the intermediary is not aware of the semantics of the negotiated extensions.
Here is a reference on close traefik bug, just for evidence: 3538
Thank you. I think that this can be closed.
I'm using traeffic web proxy that uses fragmentation of websocket messages.
Currently set to 4096B.
https://forge.tedomum.net/tedomum/traefik/blob/55f610422a8e66506a812013da1fd938a5b9c093/vendor/github.com/gorilla/websocket/conn.go
Is it some possibility to read the fragmented message in total.js?