commit b94a7b111259245c87e91297b06d3ebb4f6afb3e Author: David Fifield <david@bamsoftware.com> Date: Sat Feb 2 20:01:08 2013 -0800 Raise buffering limit from 1500 to 8192 in websocket-transport.txt. --- 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 94d4060..9904929 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 1500 octets of binary data; this may require - buffering up to 2026 bytes of UTF-8–encoded base64 text. + containing up to 8192 bytes of binary data; this may require + buffering up to 10923 bytes of UTF-8–encoded base64 text. Questions/extensions