Ian, you are not listening to the server side developers. Apache is telling you that they can't share port 80 with websocket and you're giving them nothing back! For many of us, we are already "near the HTTP spec" and it's full rules and we've already dealt with the complications. It is your attempt to simplify HTTP that is causing the complications. We've already parsed the HTTP request by the time that we know it is a websocket upgrade. We're deep inside our containers... potentially not even on the same machine that terminated the HTTP request. Nobody is saying that a compliant websocket server has to also be a fully compliant HTTP server. We are simply saying don't impose additional constraints on the format of the HTTP request/response. Allow them to be order and case insensitive and you're more or less done. There is no need to specify HTTP-lite within the websocket specification. You just refer to the HTTP upgrade mechansim and describe the extra requirements for websocket. You can constrain header values all you like - but don't constrain what the definition of a header is! regards
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.