Can't read websocket traffic using Chrome

[Johnny]

I want to read certain websocket traffic, but when using the combination of Fiddler & Chrome it is not read-able.

Inside Chrome developer tools they appear fine.  And if I use Microsoft Edge, it appears fine in Fiddler as well.

But when I use Chrome with Fiddler, it seems like there may be an extra layer of encryption or something that Fiddler doesn't handle?

Is there some setting or anything else I can tweak to make this combination work?

Attached is the view of Ping-Pong traffic as seen in Fiddler, but it isn't able to recognize these.

[Johnny]

So it appears that the difference is that Chrome negotiates permessage-deflate and if I remove the Sec-WebSocket-Extension header from the request it works.  But is there an easy way I could have Fiddler do the proper deflating instead?

[Kammen]

Hello,

Currently Fiddler doesn't support the Sec-WebSocket-Extension deflate. You can vote for this feature here.

Regards,
Kammen
Progress Telerik