> I strongly propose changing the meaning of 1007 status code from: > > 1007 indicates that an endpoint is terminating the connection > because it has received data that was supposed to be UTF-8 (such > as in a text frame) that was in fact not valid UTF-8 [RFC3629]. > > to: > > 1007 indicates that an endpoint is terminating the connection > because it has received a message that was supposed to be UTF-8 > that was in fact not valid UTF-8 [RFC3629].
This makes sense to me, given the clarification around what "messages" are. One slight revision just for succinctness: " 1007 indicates that an endpoint is terminating the connection because it has received a text message that was not valid UTF-8 [RFC3629]. " Text messages are the only ones in this spec that have to be UTF-8, and future things that are also UTF-8 should have their own error codes. Note that this is independent of whether validation is required on a frame or message level. --Richard _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
