-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,18 @@ | ||
# ProtobufInspector | ||
Protobuf Data Parser in Fiddler | ||
|
||
## Files | ||
Protobuf2Json.dll | ||
Inspectors/ProtobufInspector.dll | ||
|
||
## Usage: | ||
Copy two released files into Fiddler installation folder. | ||
|
||
Once the extension is loaded by Fiddler, it will output a log as follows: | ||
![Loading Log](https://github.com/BlueMatthew/ProtobufInspector/raw/master/docs/res/LogOnLoading.png) | ||
|
||
## How to parse the protobuf data: | ||
1. If Content-Type in response headers is "application/x-protobuf", the extension will regard it as "Protobuf" data. | ||
2. The token value of "messageType" in "Content-Type" will be regarded as message type name. | ||
3. The token value of "desc" or "Desc" in "Content-Type" will be regarded as url of descriptorset of the protos. | ||
4. If message type or descriptorset url doesn't exist, the message type name and local proto folder can be provides in Protobuf Inspector View manually and then try to parse the data. |