On Wed, Jan 29, 2014 at 12:37 PM, Mark Thomas <ma...@apache.org> wrote:
> On 29/01/2014 10:11, Martin Grigorov wrote: > > Hi, > > > > Broken - do not release. > > > > It seems WebSocket support is broken for Google Chrome 32+. > > > > I tested Apache Wicket integration and it failed with: > > WebSocket connection to > > > 'ws://localhost:8080/ws/wicket/websocket?pageId=0&wicket-ajax-baseurl=behavior?0' > > failed: Invalid UTF-8 sequence in header value > > > > So I tested Tomcat's demo apps: > > http://localhost:8080/examples/websocket/echo.xhtml > > > > And I see the same error. > > Thanks for the report. Tomcat was incorrectly sending back a value of "" > rather than not sending the header at all. I've fixed that for 7.0.x and > 8.0.x. > > I'm currently leaning towards not cancelling the release solely because > of this issue. I think there is value in making 8.0.0 available even if > 8.0.1 follows fairly quickly. My main reasoning is that this issue > exists in both 8.0.0-RC10 and 8.0.0 and overall, 8.0.0 is better quality > than 8.0.0. > I'm OK with this. I can use Firefox or older Chrome until the next release. Thanks! > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
