Can't read websocket traffic using Chrome

3 posts, 0 answers
  1. Johnny
    Johnny avatar
    2 posts
    Member since:
    Jul 2019

    Posted 02 Jul Link to this post

    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.

  2. Johnny
    Johnny avatar
    2 posts
    Member since:
    Jul 2019

    Posted 03 Jul in reply to Johnny Link to this post

    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?
  3. Kammen
    Admin
    Kammen avatar
    379 posts

    Posted 10 Jul Link to this post

    Hello,

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

    Regards,
    Kammen
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top