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 lordsutch
Recipients
Date 2002-01-07.19:39:52
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=6757

Here's my current version of the patch; the main change is that errors now result in closing the connection.  A cleaner approach for HTTP 1.1 would be to use Chunked Transfer Encoding for this, so the connection could remain available.

I still get spurious IOErrors (due to SIGPIPEs) that result from clients closing connections.  I believe this is because a lot of clients aren't well-behaved; i.e. they read the HTTP/1.1 response line then close the connection immediately.  Using TCP_CORK on Linux for sockets might help there, but it's not a general solution.  Also, I'm not really sure if these exceptions should be caught here or just left to subclasses to deal with...
History
Date User Action Args
2007-08-23 15:05:58adminlinkissue430706 messages
2007-08-23 15:05:58admincreate