**Problem phenomenon:** Because the jar package is migrated from the windows machine to the linux machine, the jar execution exception occurs as follows: java.net.SocketException: Connection reset
At the same time, there are Chinese garbled codes pushed to the DingTalk group.
**The reason is: **When setting the conn connection attribute of the facility, it is caused by setting user-agent to fiddler.
Process processing:
The Linux system executes as follows:
The normal execution on Windows is as follows:
This part sends the DingTalk robot alarm code as follows:
Original copy:
An exception is thrown according to the error message line 63:
Check the conn connection parameter information and check that the value set by user-agent is fiddler, so modify it here.
The code is adjusted to:
It has been tested that after Linux deployment, it can be pushed to the DingTalk robot normally.