Closed puellanivis closed 2 years ago
The secsh-filexfer-02 document is silent about what to do in this case. I think however the error "server unexpectedly closed connection"
might be even more clear than an unexpected EOF
.
The secsh-filexfer-02 document is silent about what to do in this case. I think however the error
"server unexpectedly closed connection"
might be even more clear than anunexpected EOF
.
I agree
Alright, I think we’re good now. 👍
Thanks!
Addresses concerns raised from #506 where a bare EOF was being returned, and thus being quite unclear about where the EOF happened.
This adds more context to the returned errors, and replaces
EOF
withUnexpectedEOF
since we definitely aren’t expecting one.However, I’m thinking a better message should be returned than even unexpected EOF. I’ll be digging through documentation to see what the best option here is.