commit 0eb274389f5967d2448c818a5f3942c2b1cc3d5f Author: David Fifield david@bamsoftware.com Date: Sat Feb 2 20:05:01 2013 -0800
Make the message size limit 16384 bytes.
I forgot that in #8126 I saw messages of 8926 bytes, bigger than the 8192-byte limit I just pushed. --- doc/websocket-transport.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/websocket-transport.txt b/doc/websocket-transport.txt index 9904929..a9d839f 100644 --- a/doc/websocket-transport.txt +++ b/doc/websocket-transport.txt @@ -180,8 +180,8 @@ Considerations specific to pluggable transports length of the next frame exceeds the limit, the endpoint MUST close the connection and SHOULD do so with a status code of 1009 (see RFC 6455 section 7.4.1). Endpoints MUST be capable of receiving messages - containing up to 8192 bytes of binary data; this may require - buffering up to 10923 bytes of UTF-8–encoded base64 text. + containing up to 16384 bytes of binary data; this may require + buffering up to 21848 bytes of UTF-8–encoded base64 text.
Questions/extensions