This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients amacd31, christian.heimes, methane, ronaldoussoren
Date 2021-01-08.13:05:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1610111125.82.0.20189778345.issue42853@roundup.psfhosted.org>
In-reply-to
Content
That's a good idea, Ronald! socket.c:sock_send_impl() already clamps the input length on Windows:

#ifdef MS_WINDOWS
    if (ctx->len > INT_MAX)
        ctx->len = INT_MAX;
    ctx->result = send(s->sock_fd, ctx->buf, (int)ctx->len, ctx->flags);
#else
    ctx->result = send(s->sock_fd, ctx->buf, ctx->len, ctx->flags);
#endif

I could implement a similar logic for SSLSocket. Applications have to check the return value of send() any way or use sendall(). The socket.send() method / send(2) libc function may also write less bytes.
History
Date User Action Args
2021-01-08 13:05:25christian.heimessetrecipients: + christian.heimes, ronaldoussoren, methane, amacd31
2021-01-08 13:05:25christian.heimessetmessageid: <1610111125.82.0.20189778345.issue42853@roundup.psfhosted.org>
2021-01-08 13:05:25christian.heimeslinkissue42853 messages
2021-01-08 13:05:25christian.heimescreate