| commit | f2b7b204a22de3f12445c237c8bd399d31b0e39b | |
| author | Olly Betts <olly@survex.com> | |
| Fri, 6 Nov 2015 06:29:45 +0000 (6 19:29 +1300) | ||
| committer | Olly Betts <olly@survex.com> | |
| Sat, 21 Nov 2015 05:22:07 +0000 (21 18:22 +1300) | ||
| tree | 419c8952cdf5fb8f364533c76c0981cecbef8c04 | treesnapshot (tar.gz zip) |
| parent | bb0539dccdc4daacbed350694e00a350458e2ed7 | commitdiff |
Stop apparent error from remote server when read-only client disconnects
A read-only client just closes the connection when done, but the server
reports "Got exception NetworkError: Received EOF", which reads like
there was a problem.
If the server gets EOF when waiting for a new command, we now just
say "Connection closed", while EOF in other circumstances is now
reported more clearly as "Connection closed unexpectedly".
Possibly fixes #654, reported by German M. Bravo.
(cherry picked from commit bcf9b05336b9ea0a53158d678c0a8084ca42e123)
A read-only client just closes the connection when done, but the server
reports "Got exception NetworkError: Received EOF", which reads like
there was a problem.
If the server gets EOF when waiting for a new command, we now just
say "Connection closed", while EOF in other circumstances is now
reported more clearly as "Connection closed unexpectedly".
Possibly fixes #654, reported by German M. Bravo.
(cherry picked from commit bcf9b05336b9ea0a53158d678c0a8084ca42e123)