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 janssen
Recipients amaury.forgeotdarc, christian.heimes, giampaolo.rodola, gvanrossum, janssen
Date 2007-12-14.16:15:15
SpamBayes Score 0.006629625
Marked as misclassified No
Message-id <4b3e516a0712140815w5dde8a66n21a258e685d1b0df@mail.gmail.com>
In-reply-to <ca471dc20712132106g309f050alab3bf1f81b88ea98@mail.gmail.com>
Content
The server isn't handling the close event properly.  I'll fix that.

On Dec 13, 2007 9:06 PM, Guido van Rossum <report@bugs.python.org> wrote:

>
> Guido van Rossum added the comment:
>
> I spoke too soon. In a debug build, this hangs forever during the
> second iteration:
>
> ./python.exe Lib/test/regrtest.py -uall -R1:1 test_ssl
>
> Adding -v, it looks like two iterations are carried out perfectly (one
> must be a trial run, one the warm-up run), but the third run goes
> beserk; the output ends like this:
>
> testAsyncoreServer (test.test_ssl.ThreadedTests) ...
>  server:  read b'over\n' from client
>  server:  closed connection <ssl.SSLSocket object, fd=6, family=2,
> type=1, proto=0>
>  server:  read b'' from client
>  server:  closed connection <ssl.SSLSocket object, fd=10, family=2,
> type=1, proto=0>
>  server:  read b'' from client
>  server:  closed connection <ssl.SSLSocket object, fd=10, family=2,
> type=1, proto=0>
> .
> . (the last two lines repeated forever)
> .
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1469>
> __________________________________
>
Files
File name Uploaded
unnamed janssen, 2007-12-14.16:15:14
History
Date User Action Args
2007-12-14 16:15:15janssensetspambayes_score: 0.00662962 -> 0.006629625
recipients: + janssen, gvanrossum, amaury.forgeotdarc, giampaolo.rodola, christian.heimes
2007-12-14 16:15:15janssenlinkissue1469 messages
2007-12-14 16:15:15janssencreate