Krixano krixano at protonmail.com
Mon Dec 13 20:55:11 GMT 2021
- - - - - - - - - - - - - - - - - - -
You know what, this whole argument was actually useless, because it's based on a portion of an outdated version of the spec, that portion of text no longer even being present in the latest version of the spec on gitlab: https://gitlab.com/gemini-specification/protocol/-/blob/master/specification.gmi
If we were to read this latest version of the spec, there is absolutely nothing in there that would precluding handling data before the close_notify. Period. Therefore, all clients that do this *are* compliant with the latest WIP version of the spec.
Additionally, it is important to quote this portion of the latest spec:
While this document just covers the protocol with some mandates for what
clients and servers have to do, there are other aspects of Gemini that
aren't covered here in the specification which fall outside the core
protocol. Implementors of both clients and servers are RECOMMENDED to
follow the best practice guide for the Gemini protocol.
and
Upon sending the complete response (which may include
content), the server closes the connection and MUST use the TLS close_notify
mechanism to inform the client that no more data will be sent.
Christian Seibold