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 jrodman2
Recipients jrodman2, orsenthil
Date 2010-11-09.06:37:04
SpamBayes Score 0.01545778
Marked as misclassified No
Message-id <1289284626.99.0.626958095636.issue10319@psf.upfronthosting.co.za>
In-reply-to
Content
shutdown isn't the same as close.
I'm not sure that's correct behavior in BaseHTTPServer depending upon whether it wants to keep the door open to weird pipeline behaviors.

Honestly, I'm having to read through tcp/ip illustrated because of this, so I'm not really the proper person to make the call.
Perhaps the bug is, as you imply, in BaseHTTPServer, not TCPServer.
History
Date User Action Args
2010-11-09 06:37:07jrodman2setrecipients: + jrodman2, orsenthil
2010-11-09 06:37:06jrodman2setmessageid: <1289284626.99.0.626958095636.issue10319@psf.upfronthosting.co.za>
2010-11-09 06:37:05jrodman2linkissue10319 messages
2010-11-09 06:37:04jrodman2create