Message 70848 - Python tracker

Message70848

Author	rharris
Recipients	cdwave, jjlee, nnorwitz, rharris
Date	2008-08-07.18:38:30
SpamBayes Score	0.007936304
Marked as misclassified	No
Message-id	<1218134314.14.0.546695402019.issue1346874@psf.upfronthosting.co.za>
In-reply-to

Content
I'm implemented the behavior described by Mike above with a patch to 2.6. The patch will raise an ExpectationFailed before sending the body if the server responds with a 417 (Expectation Failed). This patch should only modify behavior for requests that specify "Expect: 100-continue" in the request's headers. Note: The spec says that the client should send the body if the server does not respond within some reasonable period of time. This is not currently supported. Anyone have any thoughts on how that could be done?

Content

I'm implemented the behavior described by Mike above with a patch to
2.6. The patch will raise an ExpectationFailed before sending the body
if the server responds with a 417 (Expectation Failed).

This patch should only modify behavior for requests that specify
"Expect: 100-continue" in the request's headers.

Note: The spec says that the client should send the body if the server
does not respond within some reasonable period of time. This is not
currently supported. Anyone have any thoughts on how that could be done?

History
Date	User	Action	Args
2008-08-07 18:38:34	rharris	set	recipients: + rharris, nnorwitz, jjlee, cdwave
2008-08-07 18:38:34	rharris	set	messageid: <1218134314.14.0.546695402019.issue1346874@psf.upfronthosting.co.za>
2008-08-07 18:38:33	rharris	link	issue1346874 messages
2008-08-07 18:38:32	rharris	create