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 Susumu Koshiba
Recipients Susumu Koshiba, deronnax, martin.panter, r.david.murray, spaceone
Date 2016-06-05.01:04:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465088656.32.0.790765184146.issue25738@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks again for valuable comments.

I agree that there could be a case where send_error() gets used for both HEAD and GET, in which case we could send content-length field as an optional field. However, if send_error() is not used for both HEAD and GET, then the body will likely be different and RFC specifies that we must not send content-length field with different values so I have a slight preference towards not sending it for HEAD request. 

If you are OK with leaving content-length out for HEAD, I'd like to proceed with creating a small patch to reflect your comments in code review and also start creating a patches for 2.7 and 3.5.
History
Date User Action Args
2016-06-05 01:04:16Susumu Koshibasetrecipients: + Susumu Koshiba, r.david.murray, martin.panter, deronnax, spaceone
2016-06-05 01:04:16Susumu Koshibasetmessageid: <1465088656.32.0.790765184146.issue25738@psf.upfronthosting.co.za>
2016-06-05 01:04:16Susumu Koshibalinkissue25738 messages
2016-06-05 01:04:15Susumu Koshibacreate