New submission from Dima Tisnek <dim...@gmail.com>:
(apologies if this was raised before, I couldn't find it in bugs, mailing lists or discourse). (also apologies if I misunderstood something about the protocol) Up to an including TLS 1.2, a single close notify terminates both upstream and downstream; Starting with TLS 1.3 there are separate close notify alerts for upstream and downstream. This means that it's possible to have a TLS connection in half-closed state, e.g. to send "GET / HTTP xx; close notify" and then wait for the server response. Today, that's not possible, at least in asyncio, as evidenced by https://bugs.python.org/issue39951 (I did not check synchronous wrapped sockets) ---------- assignee: christian.heimes components: SSL messages: 379908 nosy: Dima.Tisnek, christian.heimes priority: normal severity: normal status: open title: Support TLS 1.3 half-closed connections type: enhancement versions: Python 3.10 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42200> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
