Websocket Open Connection - add parameter to enable compression

Issue #100 open
Nickolay Latyshev created an issue

Hi, please support ability to enable compression on connection establishing by header 'Sec-WebSocket-Extensions: permessage-deflate'

(https://tools.ietf.org/html/rfc7692)

Thank you in advance.

Comments (6)

  1. Sanjay Cherian

    Peter, you able to share where this request's priority falls and roughly when you think this can be added?

    I'm trying to make jmeter's requests behave as much as possible like those from Chrome and Firefox. That means support for "context takeover" would also be very valuable:

    https://tools.ietf.org/html/rfc7692#page-14

    Thanks a lot

  2. Peter Doornbosch repo owner

    Hi Sanjay,

    All of this wonderful software is offered to you for free. I do all this development in my spare time. So no, there are no schedules or priority list or promises, i add a feature when i feel inclined to do so.

    Regards, Peter

  3. Sanjay Cherian

    Hi Peter,

    I fully understand and definitely want to appreciate your painstaking efforts that have lead to this plugin, which many (including I) benefit from.

    If I happen to implement this request somehow, I'll create a pull request for you to review.

    Regards, Sanjay

  4. Ashwani Chhokar

    Hi @Peter Doornbosch
    Any updates/thoughts on this??
    Or you have any idea how can we just deflate/un-compress (in JMeter) the compressed messages coming from the WS Server.

    In the WS connect request, i am pushing header Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

    Response header : Sec-WebSocket-Extensions: permessage-deflate;

  5. Log in to comment