UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Build RateServer.java and ClientEventListener.java and run 'main' in the RateServer class
2. Load chat.html in Chrome preferably using a webserver on the same machine (I used a Tomcat maven plugin)
3. Type: ws://localhost:6789 into the connection URL target
4. Press the 'Connect' button.
5. The websocket onOpen method in the browser should fire allowing you to press 'Echo message' sending a message to the server. Note, the server does not echo the message back at this stage (not coded).
6. Now, to reproduce the problem...comment out the line right near the end of RateServer which is preceded with the comment "Chrome needs this...", compile and rerun the test in which the server is opting not to deflate.

In this last test, when the 'Connect' button is pressed on the chat page in the browser, the onOpen method in the client websocket isn't triggered and the 'Echo Message' button remains disabled.

What is the expected behavior?
The expected behaviour is that the websocket client, seeing no permessage-deflate in the response handshake from the server should accept the handshake from the server, trigger onOpen an proceed without deflating messages. 

What went wrong?
The javascipt API for websockets appears to insist on permessage-deflate being accepted by the server which is not true to the IETF specification.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.87  Channel: n/a
OS Version: OS X 10.9.5
Flash Version:
 

Deleted: RateServer.java 10.6 KB

RateServer.java 10.6 KB View Download

Deleted: ClientEventListener.java 164 bytes

ClientEventListener.java 164 bytes View Download

Deleted: chat.html 5.5 KB

chat.html 5.5 KB View Download