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 luiz.poleto
Recipients Kim.Gräsman, berker.peksag, luiz.poleto, terry.reedy
Date 2016-04-20.04:51:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461127906.26.0.3163262435.issue17233@psf.upfronthosting.co.za>
In-reply-to
Content
The attached patch fixes 2 of the main issues reported:

- Missing header values
- Missing newline at the end of the header line

I thought about the suggestion to include the response headers with the reply but considering that they are two different elements in an HTTP response message, I think it makes more sense to keep them on separate lines. The names, however, could be changed; perhaps from reply to response-body and headers to response-headers but maybe it could affect other users already expecting these values?
History
Date User Action Args
2016-04-20 04:51:46luiz.poletosetrecipients: + luiz.poleto, terry.reedy, berker.peksag, Kim.Gräsman
2016-04-20 04:51:46luiz.poletosetmessageid: <1461127906.26.0.3163262435.issue17233@psf.upfronthosting.co.za>
2016-04-20 04:51:46luiz.poletolinkissue17233 messages
2016-04-20 04:51:46luiz.poletocreate