These versions of the library require a custom config to USE the permessage-deflate extension. Here is a minimal example of such a custom config. You can also integrate these lines into an existing custom config.

NOTE that in these versions there is no fine grained control over which CONNECTIONS are compressed or not. Clients will request compression with the default settings and use it if the server supports it. Servers will accept whatever parameters clients request.

Outgoing messages by default will be compressed if compression was auto-negotiated during the handshake. There is an option to force a specific MESSAGE to be sent uncompressed even if compression was negotiated. This may be useful for SENDING data that you know to be compressed already (images, zip files, etc).

These versions of the library require a custom config to use the permessage-deflate extension. Here is a minimal example of such a custom config. You can also integrate these lines into an existing custom config.

Note that in these versions there is no fine grained control over which connections are compressed or not. Clients will request compression with the default settings and use it if the server supports it. Servers will accept whatever parameters clients request.

Outgoing messages by default will be compressed if compression was auto-negotiated during the handshake. There is an option to force a specific message to be sent uncompressed even if compression was negotiated. This may be useful for sending data that you know to be compressed already (images, zip files, etc).