[issue8293] HTTPSConnection.close() does not immediately close the connection.

R. David Murray added the comment: I opened issue 10127 for the ssl.SSLSocket().close() problem. -- resolution: works for me -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Antoine Pitrou added the comment: Probably, yes. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue8293] HTTPSConnection.close() does not immediately close the connection.

R. David Murray added the comment: If I'm reading this thread correctly, this bug should be closed and a new one opened about SSL socket close. Antoine, does that sound correct? -- nosy: +r.david.murray ___ Python tracker

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Tiago Teresa Teodosio added the comment: I can make the connection really get closed by running the garbage collector. It seems that the SSL socket has some kind of lazy close. import gc gc.collect() -- nosy: +TTT ___ Python tracker

[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? -- _

[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 --

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Antoine Pitrou added the comment: Works fine under a Windows XP VM too. -- resolution: out of date -> works for me status: open -> pending ___ Python tracker ___

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Antoine Pitrou added the comment: Works fine here under Linux, with 3.2, 2.6 and 2.7. HTTPS connections actually get recycled quicker than plain HTTP ones. Please note that your results could also depend on the behaviour of the target server. I tested against http://linuxfr.org. -- no

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Amaury Forgeot d'Arc added the comment: issue8524 fixed a similar issue (the timeout of the initial socket was not passed to the ssl socket). Can someone test again with a recent py3k build? -- nosy: +amaury.forgeotdarc resolution: -> out of date superseder: -> SSL sockets do not ret

[issue8293] HTTPSConnection.close() does not immediately close the connection.

David Andrzejewski added the comment: Now, it turns out that if you send the HTTP "Connection: close" header, the connection does close at the end (because the server closes it). Still, it seems like this should behave the same regardless of whether it's HTTPConnection or HTTPSConnection. --

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8293] HTTPSConnection.close() does not immediately close the connection.

Changes by Antoine Pitrou : -- nosy: +orsenthil priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue8293] HTTPSConnection.close() does not immediately close the connection.

New submission from David Andrzejewski : Python 2.6.4, Windows XP. If you run the following code: import httplib http_connection = httplib.HTTPConnection("192.168.192.196") http_connection.request("GET", "/") http_connection.sock.settimeout(20) response = http_connection.getresponse() data = r