[issue10319] SocketServer.TCPServer truncates responses on close (in some situations)

2010-11-20 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: BaseHTTPServer documentation explains that Usually, this module isn’t used directly, but is used as a basis for building functioning Web servers. Methods are usually subclassed with desirable behaviors customized. If you are using

[issue10319] SocketServer.TCPServer truncates responses on close (in some situations)

2010-11-15 Thread Ralf Schmitt
Changes by Ralf Schmitt sch...@gmail.com: -- nosy: +schmir ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10319 ___ ___ Python-bugs-list mailing

[issue10319] SocketServer.TCPServer truncates responses on close (in some situations)

2010-11-08 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: jrodman2, in the socketserver TCPServer code you will find that shutdown_request does a socket.SHUT_WR before calling close_request. If the application or code in your description used shutdown_request, instead of close_request would you

[issue10319] SocketServer.TCPServer truncates responses on close (in some situations)

2010-11-08 Thread jrodman2
jrodman2 jrod...@pythontracker.spamportal.net added the comment: 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

[issue10319] SocketServer.TCPServer truncates responses on close (in some situations)

2010-11-04 Thread jrodman2
New submission from jrodman2 jrod...@pythontracker.spamportal.net: Behavior exists in at least Python 2.5 through 3.1. The issue regards the socketserver's handling of the tcp sockets it works with. On object reaping, the sockets are properly closed (in some versions explicitly, in others