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 kristjan.jonsson
Recipients kristjan.jonsson, orsenthil, pitrou, r.david.murray, serhiy.storchaka
Date 2013-09-20.21:08:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379711325.83.0.650786679604.issue19009@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, I can make it resilient.  I was just pointing out that resilience in the face of RFC violations can be a bad thing.  E.g. Internet explorer and how they allowed internet servers of the world to be lax in how they served their data.
No matter, I can allow truncated tails when reading chunks.  But I don't think we ought to make that a requirement or make special unit tests for that.  Either you read chunked encoding correctly or you don't.  There are so many different ways you can break protocol, that this particular one is really only a special case.
History
Date User Action Args
2013-09-20 21:08:45kristjan.jonssonsetrecipients: + kristjan.jonsson, orsenthil, pitrou, r.david.murray, serhiy.storchaka
2013-09-20 21:08:45kristjan.jonssonsetmessageid: <1379711325.83.0.650786679604.issue19009@psf.upfronthosting.co.za>
2013-09-20 21:08:45kristjan.jonssonlinkissue19009 messages
2013-09-20 21:08:45kristjan.jonssoncreate