Maciej Stachowiak wrote: > OK, just to clarify, are you saying that it's specifically the > constraint on header ordering that is a problem? I'm trying to figure > out which specific requirements are problematic and why. For example, is > the requirement to have some special text in the status line acceptable? Maciej, It is mainly the header ordering and somewhat the case sensitivity. I've got no problem with the websocket server requiring special content in the status line reason. However some existing servers may have an issue as I have seen that some - in response to CRLF injection attacks on the reason string - ignore any passed value for the reason string. But I think fixes for that will in general be a lot less ugly than a fix for header ordering. cheers
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.