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 rschoon
Recipients berker.peksag, docs@python, pje, rschoon
Date 2015-02-17.17:55:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1424195747.36.0.487064838995.issue18610@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure I follow, as it has little to say on whether the application's expected behavior here, and only a recommendation that the server allow it.  But, it also defers to the "Python Standard Library", which does have an opinion.  I feel that (in hindsight) the exact behavior of each method should have been specified in full.

*However*, even if I differ on the reading of the spec, on general principle (and this has changed since I first wrote the issue) I agree that the application should not be omitting it anyway, because reading the entire response at once without checking the content length is dangerous.
History
Date User Action Args
2015-02-17 17:55:47rschoonsetrecipients: + rschoon, pje, docs@python, berker.peksag
2015-02-17 17:55:47rschoonsetmessageid: <1424195747.36.0.487064838995.issue18610@psf.upfronthosting.co.za>
2015-02-17 17:55:47rschoonlinkissue18610 messages
2015-02-17 17:55:47rschooncreate