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 scott.dial
Recipients barry, benjamin.peterson, janssen, kevinwatters, ncoghlan, r.david.murray, rhettinger, rmore, rtucker, scott.dial
Date 2009-12-09.18:24:44
SpamBayes Score 1.4694721e-06
Marked as misclassified No
Message-id <1260383087.02.0.785429385754.issue5949@psf.upfronthosting.co.za>
In-reply-to
Content
I tracked the necessary change to r73638 and issue6267. However, I am
not sure it is in scope to backport all of that.

The only changed actually needed from this set to make SocketServer
behave correctly with a SSLSocket is:

     def close_request(self, request):
         """Called to clean up an individual request."""
+        #explicitly shutdown.  socket.close() merely releases
+        #the socket and waits for GC to perform the actual close.
+        request.shutdown(socket.SHUT_WR)
         request.close()

Hence in my py26 patch, I have made a call to shutdown() within the
handler. I would call this a bug, but nobody seems to have noticed but
me, so I defer to you about the best solution.
History
Date User Action Args
2009-12-09 18:24:47scott.dialsetrecipients: + scott.dial, barry, rhettinger, ncoghlan, janssen, kevinwatters, benjamin.peterson, r.david.murray, rmore, rtucker
2009-12-09 18:24:47scott.dialsetmessageid: <1260383087.02.0.785429385754.issue5949@psf.upfronthosting.co.za>
2009-12-09 18:24:45scott.diallinkissue5949 messages
2009-12-09 18:24:44scott.dialcreate