[issue8293] HTTPSConnection.close() does not immediately close the connection.
PoltoS added the comment: I've the with module ssl. If I do sock.close() (sock is instance of ssl.SSLSocket), the connection is not closed: I see it as Established in netstat and nothing is sent over network: tcpdump show nothing going thru the network. Python 2.6.5 Linux Ubuntu -- nosy: +PoltoS status: pending -> open ___ Python tracker <http://bugs.python.org/issue8293> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8293] HTTPSConnection.close() does not immediately close the connection.
PoltoS added the comment: By the way, doing a sock.shutdown(socket.SHUT_RDWR) with a subsequent sock.close() helps to really close an SSL socket. But this may raise additional errors with subsequent close() since on some OS (like OS X) shutdown may close the socket. Am I right? -- ___ Python tracker <http://bugs.python.org/issue8293> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10127] ssl.SSLSocket().close() does not close the connection
PoltoS added the comment: After some investigations it seems that a dup() is called in ssl wrap_socket(), so on sock.close() the socket is not really closed, since there is still one more reference (file descriptor) in the kernel's tcp/ip stack. Can someone confirm this? Have not done this, but it is possible to check my supposition using linux lsof command before and after .close(). -- ___ Python tracker <http://bugs.python.org/issue10127> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
