Details
-
Suggestion
-
Resolution: Done
-
Not Evaluated
-
5.7.1
-
None
-
Debian 7 armhf with gcc 4.7.2
-
cf41cd16a1f156d68f9cb4a84dd77230f29d739f
Description
As implemented and documented for the ping method it would be highly appreciated if the close method would
- mention the 125 bytes restrictions for control frames as specified in RFC 6455 in the documentation
- automatically clipping the close reason if exceeded
Tested with jetty as a websocket client and QWebsocket as a server it is complaining in case a close reason is longer than 125 bytes :
org.eclipse.jetty.websocket.api.ProtocolException: Invalid control frame payload length, [160] cannot exceed [125]