-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fragmented frames behind proxy #46
Comments
Hi @kriskbx , |
Here's the output of
And here the new error:
Thanks a lot! |
I'm not sure I can fix this. conn.on('message', /** @param {ArrayBuffer} message */ message => messageListener(conn, doc, new Uint8Array(message))) I checked with the debugger that the A couple of things you could try:
It seems weird to me that the buffer has a size of 107kb. Was the document you created also that large? What is the size of the original Yjs document? It seems that the ArrayBuffer might have been reused, or contains data from other messages. In any case, you probably need to create another issue in the If I get around it I will upgrade the |
Describe the bug When running the WebSocket server provided in this repository behind a Traefik proxy it fails in larger documents with:
It seems that Traefik fragments frames or adapts frame size (which is compliant to the RFC). The WebSocket server uses the
arraybuffer
binary type and therefore - in my understanding - cannot deal with this. I don't understand how the y-js protocol works in detail thus I have no idea if this thing can be fixed or not.See this issue for more information: traefik/traefik#4446
To Reproduce Run the y-webserver server behind Traefik and edit a larger document so that the frame size is above 4kb.
Expected behavior The server should not fail with an error code.
Environment Information
Thanks a ton for your work, any help is highly appreciated. ❤️
Huly®: YJS-493
The text was updated successfully, but these errors were encountered: