Community
Participate
Working Groups
Build Identifier: jetty-distribution-7.1.6.v20100715 Using Jetty 7.1.6 and the stable branch of Google Chrome (6.0.472.55). Sending a message in WebSocket#onConnect via Outbound#sendMessage causes the Websocket's handshake to fail. An example snippet of code which exhibits the bug is attached. Perhaps this is not a bug, but the API does not document this. It also worked in previous versions of Jetty + Chrome. (before the hixie hixie shake). If it is not a bug, there should be a hook to know when one can actually send messages to the WebSocket. Reproducible: Always Steps to Reproduce: 1. Setup a Jetty server with the sample code 2. Run the main method 3. Connect to the server in Google Chrome 4. Click "Test" 5. The WebSocket receives an onclose event before an onopen event, representing a handshake failure.
Created attachment 178755 [details] Example Websocket Javascript client
Created attachment 178756 [details] Example Server exhibiting bug.
fixed in r2272 and a few more test harnesses added for -75, -76, -00 and -01 cheers