Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Intermittently rendering blank responses #173
Description of issue
Calling a TCP server, it is expected to always output a response. The response is always ascii strings. Simple
Using Packet Sender on both Mac and Windows I am getting intermittent blank responses rendered in the UI. I cannot find a pattern to it really. Seems to happen most when the response would be
The reason I am reporting this as an issue with Packet Sender is that nectat (nc) does not output any blank responses (for me, pretty much ruling out the TCP server as the source of the problem).
Thank you for this detailed bug report.
This is a known old problem with the TCP log in Packet Sender. A fix is still in the works. Newer versions will filter out those blank lines.
A detailed report deserves a detailed response.... if you are curious, the bug occurs as it is waiting for responses. It gets an ACK (expected) but the logger treats that like a normal packet with empty data. Thus, an empty line gets rendered in the log.
The reason this bug has persisted for so long: The core problem is the logger is not smart enough to know the difference between bare ACKS and standard packets with empty data. It seems my previous decision, log everything as an empty packet, has caused more confusion than that has helped. The next version will have that filtered.