Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Sec-WebSocket-Protocol header is private[http] #137
Comment by jrudolph
IIRC it was the conservative choice. We usually wouldn't want users to put their own WebSocket headers into requests or responses. On the other hand it is really nice to have all the headers available for unforeseen use cases. If we open them up, they should be marked somehow to be not used in normal requests or responses (unless you know what you are doing, i.e. probably reimplementing some part of akka http). If we want users to be able to actually override those headers with their own this would need to be supported in the implementation so that we don't output several potentially conflicting headers of the same kind.
Comment by ktoso
Hm, that's a good consideration I have not thought about, thanks!
~~I'm on the fence of the need of working on this issue immediately, however the immediate need as explained in the first ticket here does make sense, leaving open for someone to pick up.