I've reproduced this issue with Chrome 32.0.1700.102 and Chrome canary 34.0.1811.0.
Chrome 32 is already mainstream anyway (thanks evergreen browsers): http://clicky.com/marketshare/global/web-browsers/google-chrome/ -- Brian Clozel On Wed, Jan 29, 2014 at 4:38 PM, Yoav Shapira <yo...@apache.org> wrote: > On Wed, Jan 29, 2014 at 9:55 AM, Rossen Stoyanchev > <rstoyanc...@gopivotal.com> wrote: > > I can confirm that the issue with the empty Sec-WebSocket-Protocol header > > also affects Chrome 31.0.1650.63. > > I haven't tested 8.0.0 myself yet, but if it's broken on Chrome 31, > that's a far bigger problem than Chrome 32: > http://www.netmarketshare.com/browser-market-share.aspx?qprid=2&qpcustomd=0 > . > > Yoav > > > > > > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
