Monkeysocks Development log: TCP protocol analysis and Architecture planning

Transformation of Jsocks

First, the Company a project agent, test results: From the start to completion, only 4.7M of network traffic, the local space cost is not a problem.

Today, Jsocks was modified to replace the build tool with Maven, and became a stand-alone project Https://github.com/code4craft/jsocks. Later, the record and replay function were finished, and the possibility of various protocols replay was studied.

When replay, how to know which request corresponds to the response pack is a big problem. The starting way is to use the MD5 of the request message as the value of Key,response.

TCP protocol Analysis

Later, the Wiredshark is used to analyze with the program log.

The TCP stack is probably like this:

The following is a screenshot of the Wiredshark grab package, starting with the EA is the content of the application layer protocol.