Add Protobuf Viewer Support for WebSocket Messages

[roderickvd]

Description

Please add protobuf support for WebSocket messages in the WebSocket viewer. Currently, Proxyman supports protobuf decoding for HTTP requests and responses, but when inspecting WebSocket frames, only the Hex and Previewer views are available.

Why this feature/change is important?

Many modern APIs use WebSockets to transmit protobuf-encoded messages, especially for real-time data. Without protobuf decoding support in the WebSocket viewer, developers must manually extract and decode the binary payloads using external tools, which is time-consuming and error-prone.

Adding this feature would make Proxyman significantly more effective for debugging and reverse-engineering real-time applications using protobuf over WebSockets.

[NghiaTranUIT]

@roderickvd May I ask if your Response Header has any headers to show what the proto message type is?

[roderickvd]

Sure. Response header doesn't show it:

HTTP/1.1 101 Switching Protocols
connection: upgrade
upgrade: websocket
sec-websocket-accept: Otj0EPrAQfQ+koZ1hbqeDhozCbI=
date: Wed, 14 May 2025 18:30:36 GMT

Of course, some messages could be protobuf, some messages something else. Not saying that makes sense, but it's possible. In this particular case, all messages are protobuf-encoded but from different descriptors.

[WingCH]

Same issue, hope can support protobuf in websocket message.