I'm trying to parse some data from a socket in C#. The socket uses the Permessage-Deflate extension. While the packet types are all text, some of the packets show illegible characters.
If I select a packet and go to the HexView tab, I can right-click the packet, choose Copy/Copy as Base64, paste it into the TextWizard and then transform it from DeflatedSAML. This parsed the packet perfectly.
What is being done here in terms of encodings etc in C# equivalent code? I can't seem to go from a string received as a packet in C# to getting the same result as those steps in Fiddler, no matter what options in terms of encoding or decompression I cycle through. . .
Is there a 'flag' byte at the start of a packet that indicates whether a packet contains plain text or compressed data, out of interest?
I'd appreciate any pointers at all on this.
1 Answer, 1 is accepted
Hi Tomas,
Unfortunately, we are unable to discuss implementation details within Fiddler. However, reviewing Microsoft's Socket Example shows that the socket sends and receives bytes. Instead of working in strings it might help to work in bytes. By doing this, the Convert.ToBase64String method can enable viewing an ASCII representation.
I hope this helps. Please let me know if you need any additional information regarding Fiddler. Thank you for using the forums.
Regards,
Eric R | Senior Technical Support Engineer
Progress Telerik
Our thoughts here at Progress are with those affected by the outbreak.