💾 Archived View for rawtext.club › ~sloum › geminilist › 002142.gmi captured on 2020-09-24 at 03:19:56. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
colecmac at protonmail.com colecmac at protonmail.com
Thu Jul 9 15:38:46 BST 2020
- - - - - - - - - - - - - - - - - - -
I changed the client so it doesn't try to read the whole response before parsing
the header. And added timeout to make sure the connection is closed.
This sounds like the way to go! You can't reply on the server being compliant. I wishwe'd get a stream status code so you could know when to disable that, though...
Also for the record, my Go clients never experience this "not closing the connection"issue. Amfora attempts to load all the data before displaying it (this will change),and I've never had any problems with that on any servers. It always finds the end ofthe data fine, presumably indicated by a closed connection. Maybe the Go TLSimplementation is just more robust?
makeworld