I can confirm that the issue with the empty Sec-WebSocket-Protocol header also affects Chrome 31.0.1650.63.
The actual issue appears as an "Invalid UTF-8 sequence in header value" message in the Chrome dev tool. Although I had read what Martin reported for Chrome 32, I couldn't confirm it's the same issue since I'm on Chrome 31 and the dev tools don't even show the response headers and Firefox for some reason doesn't show the empty header. I had to use Wireshark to confirm it's the same issue. A (non-binding) vote not to release this way. This a pretty bad first-time user experience for anyone who tries 8.0. Rossen
