💾 Archived View for rawtext.club › ~sloum › geminilist › 007562.gmi captured on 2023-09-08 at 16:32:03. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Alex Schroeder alex at alexschroeder.ch
Mon Nov 8 17:07:41 GMT 2021
- - - - - - - - - - - - - - - - - - -
Regarding the closing of connections:I know from using gemini-diagnostics that my server is one of those. I just use a generic Perl async server framework and call “close_gracefully” at the end but somewhere in the layers of libraries from Mojo::IOLoop to IO::Socket::SSL to Net::SSLeay to OpenSSL somebody doesn’t handle this the way people expect it to work and I have no idea how to fix it (and I have stared at the source code of all these libraries for more hours than I cared for). So if anybody knows how to fix this using Perl, I’m interested in hearing about it. I got some helpful hints on Station so perhaps yet another look into it all will finally enlighten me.
-- Typed on a tiny keyboard. Sorry for being terse.
On 8 Nov 2021, at 15:31, Jason McBrayer <jmcbray at carcosa.net> wrote:

Stephane Bortzmeyer <stephane at sources.org> writes:
48.3 % of URLs do NOT send a proper TLS shutdown (application
close). Even 36.1 % of those who return status 20 are in that case.
Please let me know if carcosa.net is among those. Could you also post
a simple program or script for testing this? I feel like we *ought* to
be able to get server authors to fix this pretty easily, unless there
are issues with language bindings making it difficult.