💾 Archived View for rawtext.club › ~sloum › geminilist › 003036.gmi captured on 2020-11-07 at 03:18:50. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Tue Nov 3 16:26:51 GMT 2020
- - - - - - - - - - - - - - - - - - -
It was thus said that the Great Ali Fardan once stated:
On Tue, 03 Nov 2020 15:51:20 +0000
khuxkm at tilde.team wrote:
But how can I differentiate "EOF, the file is over" vs "EOF, the
socket died"?
Suppose you have content length in the header and the content received
didn't match the content length, what would you do then? What purpose
would it serve to know if it's a socket dying EOF or end of stream EOF?
Then one of the following is true if the content size doesn't match:
1. The server has a bug in that it sent a malformed size.
2. The server send a malformed file.
2. The connction was dropped during the transfer.
3. The client has a bug in counting the bytes being received.
In any case, what you have may not be complete and an error (or warning)should be presented to the operator to decide what to do next.
-spc