bug: count is not always 0 when io.EOF is encountered #2

Open
opened 6 years ago by coolaj86 · 0 comments
coolaj86 commented 6 years ago
Owner

Currently the telnet reader quits when EOF is encountered.

This happens to work correctly with Telnet, but may not work correctly with piped netcat or other clients that send the EOF fast enough for it to end up in the read buffer.

Currently the telnet reader quits when EOF is encountered. This happens to work correctly with Telnet, but may not work correctly with piped netcat or other clients that send the EOF fast enough for it to end up in the read buffer.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.