Mark, it sounds like Jetty is not "seeing" the request as a websocket upgrade request.
This is likely to be caused by your browser speaking a different dialect of websocket (as the drafts have been changing pretty quickly). I would suggest trying jetty-7.4 that speaks more versions of websockets. cheers On 24 April 2011 01:16, Mark Swinson <[email protected]> wrote: > > Hi all, > > I’m playing with the jetty websocket chat example that comes with the jetty > distribution, > ( I’m currently using jetty 7.2.0 and I’m running a stand alone instance of > the server ). > > However when I open a websocket , ( or when I try and simulate it using a > REST client ) > I get the response Unrecognised response: 200. It seems to hit the get > request and does > not hit the doGetWebSocketConnect method in the chat servlet. > > I think I have a good understanding of what is going on in the client side > code, so I think > its something to do with my configuration of the server. > > Has anyone else experienced this and can help? > > > Thanks > > > Mark > > > > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
