[issue17233] http.client header debug output format

Change by STINNER Victor : -- keywords: -easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17233] http.client header debug output format

Kim Gräsman added the comment: Thanks! I filed this so long ago that I'd forgotten about it. I ran the code in question with your patch manually hacked into my Python installation (3.4.1) and output is much easier to digest now. I don't have a strong opinion on key names -- I haven't needed

[issue17233] http.client header debug output format

Changes by Luiz Poleto : -- nosy: +luiz.poleto ___ Python tracker ___ ___

[issue17233] http.client header debug output format

Changes by Berker Peksag : -- keywords: +easy nosy: +berker.peksag stage: -> needs patch versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4 ___ Python tracker

[issue17233] http.client header debug output format

Terry J. Reedy added the comment: The doc is vague on debug output (intentionally so, I suspect). Any value greater than 0 will cause all currently defined debug output to be printed to stdout. I agree that send: and reply: should be formatted the same, so the reply: line should include the

[issue17233] http.client header debug output format

Kim Gräsman added the comment: Thanks for your response! I agree that send: and reply: should be formatted the same, so the reply: line should include the headers *with* the values. OK, yeah, that would avoid having to specify request/response for headers as well, I think. The current

[issue17233] http.client header debug output format

New submission from Kim Gräsman: Python 3.2.3 on 64-bit Windows 7. When I set debuglevel on HTTPConnection to 1, the output seems jumbled, and I'm having trouble interpreting it. Attached is a full, anonymized log from a conversation I was troubleshooting. Here's an excerpt: send: b'GET /a